Triple
T23712206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apollo 5 |
E585896
|
entity |
| Predicate | LMDescentEngineTested |
P153662
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Apollo 5, LMDescentEngineTested, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: LMDescentEngineTested Context triple: [Apollo 5, LMDescentEngineTested, true]
-
A.
descentMethod
Indicates the technique or process used to descend from a higher position, level, or altitude.
-
B.
approximateDescentTime
Indicates an estimated or calculated time at which a descent event is expected to occur.
-
C.
hasDescent
Indicates that one entity is a descendant of another, typically through a lineage or ancestry relationship.
-
D.
descentVia
Indicates a lineage relationship where one entity is descended from another through one or more intermediate generations or branches.
-
E.
developedEngine
Indicates that one entity created, designed, or engineered an engine for another entity or purpose.
- 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_69e24905f77881908194d645676acd60 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b7784cd08190a442dd41d56b92b1 |
completed | April 29, 2026, 7:47 a.m. |
| PD | Predicate disambiguation | batch_69f155e4b1148190836ede4741dcb888 |
completed | April 29, 2026, 12:50 a.m. |
| PDg | Predicate description generation | batch_69f15b453da88190889a8d9b21727958 |
completed | April 29, 2026, 1:13 a.m. |
Created at: April 17, 2026, 6:54 p.m.