Triple
T2882423
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Super Heavy booster |
E59426
|
entity |
| Predicate | engineArrangement |
P22132
|
FINISHED |
| Object | central and outer ring clusters |
—
|
LITERAL FINISHED |
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: central and outer ring clusters | Statement: [Super Heavy booster, engineArrangement, central and outer ring clusters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: engineArrangement Context triple: [Super Heavy booster, engineArrangement, central and outer ring clusters]
-
A.
enginePlacement
chosen
Indicates the spatial or structural position where an engine is located or mounted relative to another object or system.
-
B.
wheelArrangementSystem
Indicates the specific configuration or system by which the wheels of a vehicle or rolling stock are arranged and organized.
-
C.
numberOfCylinders
Indicates the count of engine cylinders associated with an entity.
-
D.
cylinderArrangement
Indicates how multiple cylinders are positioned or organized relative to one another.
-
E.
availableEngineDisplacement
Indicates the range or specific values of engine displacement that are offered or applicable for a given entity.
- 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_69ab4ac739188190a112f42a5a69c951 |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abe02aa5948190a2e0bd9168232bd5 |
completed | March 7, 2026, 8:22 a.m. |
| PD | Predicate disambiguation | batch_69abdd15cbf08190bf7fea5ea516848a |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:03 p.m.