Triple
T33839794
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apollo 15 subsatellite |
E867326
|
entity |
| Predicate | missionDurationAfterRelease |
P13423
|
FINISHED |
| Object | several months |
—
|
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: several months | Statement: [Apollo 15 subsatellite, missionDurationAfterRelease, several months]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: missionDurationAfterRelease Context triple: [Apollo 15 subsatellite, missionDurationAfterRelease, several months]
-
A.
missionDuration
chosen
Indicates the length of time over which a mission or operation takes place from start to finish.
-
B.
missionDurationPlanned
Indicates the length of time that a mission is scheduled or intended to last according to its plan.
-
C.
missionDurationType
Indicates the classification of a mission’s length or time span (e.g., short-term, long-term, extended).
-
D.
missionDurationCapability
Indicates the length of time an entity is capable of sustaining or performing a mission or operation.
-
E.
timeOfMission
Indicates the specific time or period during which a mission takes place or is scheduled.
- 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_69f34992ad40819087760ed939bd2a7a |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7764ab1fc81909f9348db87bd7692 |
completed | May 3, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69f76905d9c88190b1ee810bc9ab644f |
completed | May 3, 2026, 3:25 p.m. |
Created at: May 1, 2026, 1:47 a.m.