Triple
T13444728
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GT-5 |
E320449
|
entity |
| Predicate | isPredecessorTo |
P80614
|
FINISHED |
| Object | Apollo program long-duration missions |
—
|
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: Apollo program long-duration missions | Statement: [GT-5, isPredecessorTo, Apollo program long-duration missions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPredecessorTo Context triple: [GT-5, isPredecessorTo, Apollo program long-duration missions]
-
A.
isSuccessorTo
Indicates that one entity directly follows another in an ordered sequence, coming immediately after it.
-
B.
predecessorRelationship
chosen
Indicates that one entity comes before another in an ordered sequence, chain, or lineage, serving as its prior or earlier counterpart.
-
C.
contributedToPredecessorOf
Indicates that one entity contributed to or influenced another entity that came before a specified successor in a sequence or lineage.
-
D.
predecessorStateOf
Indicates that one state occurs immediately before and leads into another state in a sequence or process.
-
E.
hasPredecessorStructureFrom
Indicates that one structure existed or was established before another structure in a sequential or developmental order.
- 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_69d80761e6cc8190a90c844589998ecc |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbaef5f610819092cad33ef72075ff |
completed | April 12, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69d9a03ce03481908c61094f0cc0c158 |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:40 p.m.