Triple
T5582267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eagle |
E146666
|
entity |
| Predicate | EVALunarSurfaceDuration |
P38136
|
FINISHED |
| Object | about 2 hours 15 minutes |
—
|
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: about 2 hours 15 minutes | Statement: [Eagle, EVALunarSurfaceDuration, about 2 hours 15 minutes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: EVALunarSurfaceDuration Context triple: [Eagle, EVALunarSurfaceDuration, about 2 hours 15 minutes]
-
A.
timeOnLunarSurface
Indicates the duration that an entity spends on the surface of the Moon.
-
B.
actualMissionDurationOnSurface
Indicates the length of time that a mission actually spent on the surface, as opposed to planned or total mission duration.
-
C.
totalEVAOnMoonDuration
chosen
Indicates the total amount of time an entity has spent performing extravehicular activities (EVAs) on the Moon.
-
D.
missionDurationFromLaunchToImpact
Indicates the total elapsed time between the launch of a mission and the moment of its impact.
-
E.
evaCountOnLunarSurface
Indicates the number of extravehicular activities (spacewalks) performed on the lunar surface.
- 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_69c0090287a08190b4098411effe970c |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c0208333f08190bf0049b6bdd280f5 |
completed | March 22, 2026, 5:01 p.m. |
| PD | Predicate disambiguation | batch_69c01b147cc081909237f3f2967d4cb8 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:37 p.m.