Triple
T29323049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SpinLaunch |
E743562
|
entity |
| Predicate | hasCustomerAgreement |
P188783
|
FINISHED |
| Object | NASA |
—
|
NE NERFINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: NASA | Statement: [SpinLaunch, hasCustomerAgreement, NASA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCustomerAgreement Context triple: [SpinLaunch, hasCustomerAgreement, NASA]
-
A.
hasTypeOfAgreement
Indicates that one entity is associated with, or governed by, a specific category or type of agreement.
-
B.
hasAgreementSystem
Indicates that there exists a specific grammatical agreement system (e.g., for features like number, gender, or person) associated with the given entity.
-
C.
implementsAgreementWith
Indicates that one party carries out or fulfills the terms of an agreement made with another party.
-
D.
requiresAgreementWith
Indicates that one entity’s action, decision, or validity is contingent upon obtaining consent or formal agreement from another specified entity.
-
E.
canEnterIntoAgreementsWith
Indicates that one entity has the legal or formal capacity to make binding agreements or contracts with another entity.
- F. None of above. chosen
Provenance (4 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f09125f784819080f4e9fce9fe624f |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69fbad1e94988190b86d447a68e65067 |
completed | May 6, 2026, 9:05 p.m. |
| PD | Predicate disambiguation | batch_69fba881b8e0819094790935152b99a1 |
completed | May 6, 2026, 8:45 p.m. |
| PDg | Predicate description generation | batch_69fbad1b3ba08190ad69e21461333f2e |
completed | May 6, 2026, 9:05 p.m. |
Created at: April 28, 2026, 1:24 p.m.