Triple
T34643622
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apollo 12 landing site |
E889635
|
entity |
| Predicate | totalSurfaceTime_hours |
P43134
|
FINISHED |
| Object | about 31.5 |
—
|
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 31.5 | Statement: [Apollo 12 landing site, totalSurfaceTime_hours, about 31.5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: totalSurfaceTime_hours Context triple: [Apollo 12 landing site, totalSurfaceTime_hours, about 31.5]
-
A.
durationTotal
chosen
Indicates the overall length of time for which an event, process, or state persists, typically aggregating all its constituent durations.
-
B.
spentTimeIn
Indicates that an entity has spent a certain amount or period of time in a particular place or context.
-
C.
endTimeDetail
Indicates the specific or refined information about when an event, action, or state concludes.
-
D.
actualDuration
Indicates the real amount of time that an event, process, or activity actually took to complete, as opposed to its planned or estimated duration.
-
E.
timeToComplete
Indicates the duration required for an entity or process to be fully completed.
- 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_69f9fd6834cc8190aa27153d6a99f3bb |
completed | May 5, 2026, 2:23 p.m. |
| PD | Predicate disambiguation | batch_69f7cf769338819092a5f42653dcc956 |
completed | May 3, 2026, 10:43 p.m. |
Created at: May 1, 2026, 2:04 a.m.