Triple
T29105405
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tokitae |
E736748
|
entity |
| Predicate | endTimeAtLocation |
P121592
|
FINISHED |
| Object | 2023 |
—
|
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: 2023 | Statement: [Tokitae, endTimeAtLocation, 2023]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endTimeAtLocation Context triple: [Tokitae, endTimeAtLocation, 2023]
-
A.
timeOfJourneyEnd
Indicates the point in time at which a journey or trip concludes.
-
B.
previousLocationTime
Indicates the specific time at which an entity was located at its immediately preceding location before its current one.
-
C.
locatedAtTime
chosen
Indicates that a location relationship holds during a specific time or time interval.
-
D.
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.
-
E.
endLocationOfJourney
Indicates the final destination or stopping point reached at the conclusion of a journey or trip.
- 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_69f077ec765c81909474c88bcc8bab43 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69fba2877b248190a974eb092243c0c4 |
completed | May 6, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69fb8d06a1b48190a937aa410d159dfa |
completed | May 6, 2026, 6:48 p.m. |
Created at: April 28, 2026, 11:15 a.m.