Triple
T35345088
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | STS-5 |
E1020718
|
entity |
| Predicate | spaceShuttleOrbiterDesignation |
P21490
|
FINISHED |
| Object | OV-102 |
—
|
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: OV-102 | Statement: [STS-5, spaceShuttleOrbiterDesignation, OV-102]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spaceShuttleOrbiterDesignation Context triple: [STS-5, spaceShuttleOrbiterDesignation, OV-102]
-
A.
SpaceShuttleOrbiter
Indicates that an entity functions as a space shuttle orbiter, specifically the reusable winged spacecraft component of a space shuttle system.
-
B.
orbiterDesignation
chosen
Indicates that one entity is designated as an orbiter (spacecraft or object in orbit) associated with another entity.
-
C.
orbiterName
Indicates the name assigned to an orbiter associated with a particular mission or celestial body.
-
D.
orbiterType
Indicates the specific class or category of an orbiter based on its design, mission role, or operational characteristics.
-
E.
orbiterNumber
Indicates the identifying number assigned to a specific orbiter associated with an object or mission.
- 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_69f76decd95c8190ae428f6a19d535de |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f79da9f80c8190b0afd8509f28747b |
completed | May 3, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69f79617d40481909ba372f94209c08b |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:03 p.m.