Triple
T20079810
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UTDC ALRV |
E499966
|
entity |
| Predicate | serviceWithdrawalStartYear |
P26460
|
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: [UTDC ALRV, serviceWithdrawalStartYear, 2018]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceWithdrawalStartYear Context triple: [UTDC ALRV, serviceWithdrawalStartYear, 2018]
-
A.
cancellationYear
chosen
Indicates the year in which something (such as an event, contract, or service) was officially canceled or terminated.
-
B.
eligibilityPeriodStartYear
Indicates the calendar year in which an entity’s eligibility period begins.
-
C.
contractStartYear
Indicates the calendar year in which a contract between parties officially begins.
-
D.
exitYear
Indicates the year in which an entity leaves, finishes, or ceases its association with another entity or context.
-
E.
startServiceYear
Indicates the year in which an entity began providing a particular service or started its service-related activity.
- 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_69da627770948190997f486f9a2e370f |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6643f93208190ae2a413f88ea9aed |
completed | April 20, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69e54cf369b88190931532420517dac7 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:40 p.m.