Triple
T249380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NASA Space Shuttle program |
E5108
|
entity |
| Predicate | cargoBayLength |
P8798
|
FINISHED |
| Object | 18.3 meters |
—
|
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: 18.3 meters | Statement: [NASA Space Shuttle program, cargoBayLength, 18.3 meters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cargoBayLength Context triple: [NASA Space Shuttle program, cargoBayLength, 18.3 meters]
-
A.
hasBaggageSystem
Indicates that an entity is equipped with or utilizes a baggage handling system.
-
B.
hasCargoTerminal
Indicates that a location or facility includes or is equipped with a cargo terminal for handling freight.
-
C.
carriedBy
Indicates that one entity is physically supported and transported by another entity.
-
D.
mainCargo
Indicates that one entity serves as the primary or principal cargo carried or transported by another entity.
-
E.
aircraftTypesCarried
Indicates that one entity (typically a vessel, facility, or platform) carries or is capable of carrying specific types of aircraft as part of its operations or configuration.
- 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_69a257c4bf688190a46ebbf411ab7473 |
completed | Feb. 28, 2026, 2:49 a.m. |
| NER | Named-entity recognition | batch_69a25d3728f0819086214ccc2db2305a |
completed | Feb. 28, 2026, 3:12 a.m. |
| PD | Predicate disambiguation | batch_69a25b64ea3081908de626a0e1445bdb |
completed | Feb. 28, 2026, 3:05 a.m. |
| PDg | Predicate description generation | batch_69a25c2ca46c81908c61696f31e59a98 |
completed | Feb. 28, 2026, 3:08 a.m. |
Created at: Feb. 28, 2026, 2:54 a.m.