Triple
T3430531
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lost Moon |
E72324
|
entity |
| Predicate | workChronologyContext |
P32272
|
FINISHED |
| Object | Apollo program literature |
—
|
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 literature | Statement: [Lost Moon, workChronologyContext, Apollo program literature]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workChronologyContext Context triple: [Lost Moon, workChronologyContext, Apollo program literature]
-
A.
workChronologyPosition
Indicates the relative ordering or position of a work within a sequence of works, such as in a career, series, or catalog.
-
B.
workChronicles
chosen
Indicates that one entity documents, records, or narrates the work-related activities, history, or experiences of another entity.
-
C.
involvesChronology
Indicates that the relationship or action explicitly depends on, references, or organizes events according to their order or position in time.
-
D.
chronologicalFunction
Indicates a temporal relationship where one event or state functions to order, structure, or position another within a sequence of time.
-
E.
chronologicallyCovers
Indicates that one time period, event, or sequence extends over and includes the entire chronological span of another.
- 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_69ad85ae14308190bcbc25cfa0246c0b |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb9bd61908190a7bdd01f24334fc3 |
completed | March 8, 2026, 6:02 p.m. |
| PD | Predicate disambiguation | batch_69adadfea024819094b41a13bc004bda |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:15 p.m.