Triple
T38479438
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Command Module C-020 |
E915629
|
entity |
| Predicate | predecessorInProgram |
P197506
|
FINISHED |
| Object | Apollo 4 command module C-017 |
—
|
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: Apollo 4 command module C-017 | Statement: [Command Module C-020, predecessorInProgram, Apollo 4 command module C-017]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: predecessorInProgram Context triple: [Command Module C-020, predecessorInProgram, Apollo 4 command module C-017]
-
A.
successorInProgram
Indicates that one element in a program directly follows another in the program’s execution or structural order.
-
B.
predecessorCode
Indicates that one code directly precedes another code in a defined sequence or versioning order.
-
C.
predecessorFunction
Indicates a function that maps each element to its immediate predecessor in an ordered sequence or structure.
-
D.
programPredecessor
Indicates that one program temporally or logically precedes another in a sequence or hierarchy of programs.
-
E.
intendedPredecessorOf
Indicates that one entity is meant or planned to come before another in a sequence, order, or process.
- 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_69f76e8ff5cc8190a88803369183845e |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fe96c2647c819082989f11e1ae3d35 |
completed | May 9, 2026, 2:06 a.m. |
| PD | Predicate disambiguation | batch_69fe928615448190af939e5a94be55bb |
completed | May 9, 2026, 1:48 a.m. |
| PDg | Predicate description generation | batch_69fe96c0b760819093737292d33df165 |
completed | May 9, 2026, 2:06 a.m. |
Created at: May 3, 2026, 4:31 p.m.