Triple
T7780409
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Columbia |
E221498
|
entity |
| Predicate | orbiterType |
P78968
|
FINISHED |
| Object | Block I orbiter |
—
|
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: Block I orbiter | Statement: [Columbia, orbiterType, Block I orbiter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orbiterType Context triple: [Columbia, orbiterType, Block I orbiter]
-
A.
orbiterNumber
Indicates the identifying number assigned to a specific orbiter associated with an object or mission.
-
B.
orbiterDesignation
Indicates that one entity is designated as an orbiter (spacecraft or object in orbit) associated with another entity.
-
C.
orbiterFleet
Indicates that one entity is part of, or belongs to, a fleet of orbiting spacecraft associated with another entity.
-
D.
notableOrbiter
Indicates that one entity is a particularly significant or well-known artificial satellite or spacecraft that orbits another entity.
-
E.
otherOrbiterName
Indicates that one orbiter is identified or referred to by an alternative or secondary name.
- 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_69ca83ebbef881909ac47f789145fef7 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cae7e779ec8190b77296d9c2ac3210 |
completed | March 30, 2026, 9:15 p.m. |
| PD | Predicate disambiguation | batch_69caa488532c819093ac40bba0b3c7ef |
completed | March 30, 2026, 4:27 p.m. |
| PDg | Predicate description generation | batch_69cae7e47c5c8190bca90d45b3cdc25e |
completed | March 30, 2026, 9:15 p.m. |
Created at: March 30, 2026, 4:20 p.m.