Triple
T10700933
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apollo 9 |
E252271
|
entity |
| Predicate | crewCallsign |
P1565
|
FINISHED |
| Object | Gumdrop for Command Module |
—
|
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: Gumdrop for Command Module | Statement: [Apollo 9, crewCallsign, Gumdrop for Command Module]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crewCallsign Context triple: [Apollo 9, crewCallsign, Gumdrop for Command Module]
-
A.
callsign
chosen
Indicates that an entity is assigned or uses a specific radio or identification callsign as its designated identifier in communication contexts.
-
B.
icaoCallsignFor
Indicates that one entity is the ICAO-assigned callsign used in air traffic communications for the other entity (typically an airline or aircraft operator).
-
C.
towerCallsign
Indicates that an entity serves as the radio callsign identifier used by an air traffic control tower when communicating.
-
D.
formerCallSign
Indicates that one identifier was previously used as the call sign for the other entity before being changed or replaced.
-
E.
callsignOfOperator
Indicates that one entity is the radio or communication callsign assigned to or used by another entity acting as an operator.
- 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_69d6aa5cbabc8190973e683950d89faf |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6fd8bb7408190a350840e1df3b910 |
completed | April 9, 2026, 1:14 a.m. |
| PD | Predicate disambiguation | batch_69d6dd8cc0788190b4c02a772e4b58b3 |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 9:12 p.m.