Triple
T34556935
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apollo 8 spacecraft |
E887228
|
entity |
| Predicate | tliBurnPerformedBy |
P30855
|
FINISHED |
| Object | Saturn V S-IVB stage |
—
|
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: Saturn V S-IVB stage | Statement: [Apollo 8 spacecraft, tliBurnPerformedBy, Saturn V S-IVB stage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tliBurnPerformedBy Context triple: [Apollo 8 spacecraft, tliBurnPerformedBy, Saturn V S-IVB stage]
-
A.
isConductedBy
chosen
Indicates that an event, activity, or process is carried out, organized, or overseen by a particular agent or entity.
-
B.
burningAssistedBy
Indicates that a burning process or fire is enabled, supported, or facilitated by another agent, substance, or factor.
-
C.
hasBurnUnit
Indicates that one entity (typically a medical facility) includes or is equipped with a specialized unit dedicated to the treatment and care of burn patients.
-
D.
burnedAt
Indicates that something was subjected to burning at a specific time or in a specific event.
-
E.
laterPerformedBy
Indicates that an action or event is carried out by a particular agent at a later time than another referenced action or event.
- 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_69f349d0c4d881908dd0950f5eb9ec0a |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7206085d08190bf62da716a91fdcb |
completed | May 3, 2026, 10:16 a.m. |
| PD | Predicate disambiguation | batch_69f71cc8074c81909ae09bea2acf1a09 |
completed | May 3, 2026, 10 a.m. |
Created at: May 1, 2026, 2:02 a.m.