Triple
T31986052
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Expedition 29 |
E816723
|
entity |
| Predicate | durationApproximateDays |
P172309
|
FINISHED |
| Object | 66 |
—
|
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: 66 | Statement: [Expedition 29, durationApproximateDays, 66]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: durationApproximateDays Context triple: [Expedition 29, durationApproximateDays, 66]
-
A.
durationDaysApprox
chosen
Indicates an approximate length of time, measured in days, for which an event, state, or condition lasts.
-
B.
endTimeApproximate
Indicates that the recorded end time of an event or action is not exact but an approximate value.
-
C.
typicalDurationDays
Indicates the usual or expected number of days that an associated event, process, or state typically lasts.
-
D.
deliveryDays
Indicates the number of days required for an item or service to be delivered from the sender to the recipient.
-
E.
intendedDuration
Indicates the planned or expected length of time for which an action, event, or state is meant to occur or remain in effect.
- 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_69f348f8002081909a3588758ba94afb |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b3b1045081908ba99d7a84d03649 |
completed | May 3, 2026, 2:32 a.m. |
| PD | Predicate disambiguation | batch_69f6b151ad008190836c1bcdec503ce2 |
completed | May 3, 2026, 2:22 a.m. |
Created at: May 1, 2026, 12:12 a.m.