Triple
T10582112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Los Pinos |
E249760
|
entity |
| Predicate | useEndTime |
P37807
|
FINISHED |
| Object | 2018 |
—
|
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: 2018 | Statement: [Los Pinos, useEndTime, 2018]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: useEndTime Context triple: [Los Pinos, useEndTime, 2018]
-
A.
endTimeAsCapital
Indicates that a specified time marks the ending point of an event, process, or state in the role of its designated capital or primary endpoint.
-
B.
typicallyEndsAt
Indicates that an event, process, or activity most commonly or usually concludes at a particular time, place, or state.
-
C.
statusEndsWhen
Indicates that a particular status or condition ceases to hold when a specified event, time, or state occurs.
-
D.
timeOfSettingEnd
Indicates the point in time at which a specified setting, condition, or configuration ceases to be in effect.
-
E.
setsTermEndDateFor
chosen
Indicates setting or assigning the end date of a term or period for another entity.
- 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_69d381c9d3d48190a29ee491e1696a0e |
completed | April 6, 2026, 9:50 a.m. |
| NER | Named-entity recognition | batch_69d52766d53c8190b51753768ab58c31 |
completed | April 7, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69d51907b2b881908ab9a8594688ee06 |
completed | April 7, 2026, 2:47 p.m. |
Created at: April 6, 2026, 12:39 p.m.