Triple
T24933761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metcard |
E623257
|
entity |
| Predicate | lastDayOfUse |
P157251
|
FINISHED |
| Object | 2012-12-29 |
—
|
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: 2012-12-29 | Statement: [Metcard, lastDayOfUse, 2012-12-29]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lastDayOfUse Context triple: [Metcard, lastDayOfUse, 2012-12-29]
-
A.
lastYearOfUse
Indicates the final year in which something was actively used or in operation.
-
B.
lastUsedFor
Indicates that one entity was the most recent purpose, function, or application for which another entity was used.
-
C.
usedToDate
Indicates that two entities were previously in a romantic or dating relationship but are no longer together.
-
D.
lastEntryDate
Indicates the date on which the most recent entry, record, or update associated with the subject occurred.
-
E.
lastODIDate
Indicates the date on which the most recent OD (overdraft or overdraft-related) event or record occurred for the associated entity.
- F. None of above. chosen
Provenance (4 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_69e2fac6b5a48190a1c38857f00915a9 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f423b654e48190b9a073a67cbf82f3 |
completed | May 1, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69f4210130d08190ae30b7943f7a0bbc |
completed | May 1, 2026, 3:41 a.m. |
| PDg | Predicate description generation | batch_69f423637bec8190a1701421ac86a3b7 |
completed | May 1, 2026, 3:52 a.m. |
Created at: April 18, 2026, 5:30 a.m.