Triple
T37414668
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apollo 17 Lunar Module Challenger |
E929666
|
entity |
| Predicate | rejoinedWith |
P147224
|
FINISHED |
| Object | Apollo 17 Command and Service Module America |
—
|
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 17 Command and Service Module America | Statement: [Apollo 17 Lunar Module Challenger, rejoinedWith, Apollo 17 Command and Service Module America]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rejoinedWith Context triple: [Apollo 17 Lunar Module Challenger, rejoinedWith, Apollo 17 Command and Service Module America]
-
A.
reunitedIn
Indicates that entities who were previously separated have come together again at a specific time or place.
-
B.
reunionWith
chosen
Indicates that two or more entities come back together after a period of separation or absence.
-
C.
reunitedAs
Indicates that entities who were previously separated have come back together or been brought back into association.
-
D.
reunitedFor
Indicates that entities who were previously separated have come back together or been brought back into association.
-
E.
reintegratedInto
Indicates that an entity has been brought back and incorporated again into a group, system, or context it was previously separated from.
- 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_69f76ebde49481908566cd96b37ccc84 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb9e1845e881908d19158440cf3b87 |
completed | May 6, 2026, 8:01 p.m. |
| PD | Predicate disambiguation | batch_69fb8d08d6988190a00794ac26078348 |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 3, 2026, 4:16 p.m.