Triple
T35230700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | STS-3 |
E1017224
|
entity |
| Predicate | crewCalls |
P182634
|
FINISHED |
| Object | Columbia |
—
|
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: Columbia | Statement: [STS-3, crewCalls, Columbia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crewCalls Context triple: [STS-3, crewCalls, Columbia]
-
A.
crewChief
Indicates that one person serves as the lead or supervising crew chief responsible for directing and managing another person or group in an operational context.
-
B.
castBell
Indicates that an entity creates or forms a bell by pouring molten material into a mold or otherwise shaping it.
-
C.
inspiredCallsignOf
Indicates that one entity’s callsign was created based on, influenced by, or derived from another entity.
-
D.
callsign
Indicates that an entity is assigned or uses a specific radio or identification callsign as its designated identifier in communication contexts.
-
E.
towerCallsign
Indicates that an entity serves as the radio callsign identifier used by an air traffic control tower when communicating.
- 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_69f76de12e4c8190bc46b71a32858356 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7904a770481908ef3f788e51e8dba |
completed | May 3, 2026, 6:13 p.m. |
| PD | Predicate disambiguation | batch_69f78e2d71248190b850c2802ec170c0 |
completed | May 3, 2026, 6:04 p.m. |
| PDg | Predicate description generation | batch_69f78f629d508190b755848162c4e101 |
completed | May 3, 2026, 6:09 p.m. |
Created at: May 3, 2026, 4:02 p.m.