Triple
T38125534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Falcon 9 Flight 1 |
E952056
|
entity |
| Predicate | payloadManufacturer |
P141772
|
FINISHED |
| Object | SpaceX |
—
|
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: SpaceX | Statement: [Falcon 9 Flight 1, payloadManufacturer, SpaceX]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: payloadManufacturer Context triple: [Falcon 9 Flight 1, payloadManufacturer, SpaceX]
-
A.
manufacturerType
Indicates the classification or category of a manufacturer based on its role, characteristics, or production type.
-
B.
representsManufacturer
chosen
Indicates that one entity is the manufacturer or producer responsible for making another entity.
-
C.
radarManufacturer
Indicates that one entity is the manufacturer or producer of a radar system used or associated with another entity.
-
D.
usedManufacturer
Indicates that an entity has employed or sourced products, components, or services from a particular manufacturer.
-
E.
manufacturerCode
Indicates the unique code assigned by a manufacturer to identify a specific product, component, or item it produces.
- F. None of above.
Provenance (3 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_69f76f083548819082bd2bbf53c79e8e |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fc4748843c8190931432653be4890c |
completed | May 7, 2026, 8:03 a.m. |
| PD | Predicate disambiguation | batch_69fc45646ce481908caf292ff9f06e15 |
completed | May 7, 2026, 7:55 a.m. |
Created at: May 3, 2026, 4:21 p.m.