Triple
T34643623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apollo 12 landing site |
E889635
|
entity |
| Predicate | totalEVATime_hours |
P43134
|
FINISHED |
| Object | about 7.75 |
—
|
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 7.75 | Statement: [Apollo 12 landing site, totalEVATime_hours, about 7.75]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: totalEVATime_hours Context triple: [Apollo 12 landing site, totalEVATime_hours, about 7.75]
-
A.
evaDuration
Indicates the length of time that an extravehicular activity (EVA) lasts or is scheduled to last.
-
B.
endTimeDetail
Indicates the specific or refined information about when an event, action, or state concludes.
-
C.
timeEquivalentOf
Indicates that two temporal entities represent the same point in time or duration, possibly expressed in different formats or units.
-
D.
timeOfCharging
Indicates the specific time or period during which a charging event occurs.
-
E.
durationTotal
chosen
Indicates the overall length of time for which an event, process, or state persists, typically aggregating all its constituent durations.
- 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_69f349d825c88190bfc6170ac9281260 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fb2e940d5c8190bceae77daf4ef512 |
completed | May 6, 2026, 12:05 p.m. |
| PD | Predicate disambiguation | batch_69f9fec70bd881909c658a3c5020318b |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 1, 2026, 2:04 a.m.