Triple
T33839548
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apollo 15 landing site |
E867321
|
entity |
| Predicate | totalSurfaceStayDuration |
P43134
|
FINISHED |
| Object | about 66 hours |
—
|
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 66 hours | Statement: [Apollo 15 landing site, totalSurfaceStayDuration, about 66 hours]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: totalSurfaceStayDuration Context triple: [Apollo 15 landing site, totalSurfaceStayDuration, about 66 hours]
-
A.
stayDurationFocus
Indicates the length of time an entity remains at or engaged with a particular place, activity, or context as the primary focus.
-
B.
durationTotal
chosen
Indicates the overall length of time for which an event, process, or state persists, typically aggregating all its constituent durations.
-
C.
commonDuration
Indicates that two or more events, actions, or states share the same length of time.
-
D.
surfaceOperationsDuration
Indicates the length of time that surface-related operations or activities are carried out.
-
E.
durationPerParticipant
Indicates the amount of time associated with or allocated to each individual participant in the related activity 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_69f34992ad40819087760ed939bd2a7a |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7b2f3a104819098ddd8909eaf596c |
completed | May 3, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f7b1b8a9fc8190a1279e67a2d12707 |
completed | May 3, 2026, 8:36 p.m. |
Created at: May 1, 2026, 1:47 a.m.