Triple
T37953030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Luxembourg national public transport system |
E946792
|
entity |
| Predicate | fareAbolitionEffectiveDate |
P159872
|
FINISHED |
| Object | 2020-03-01 |
—
|
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: 2020-03-01 | Statement: [Luxembourg national public transport system, fareAbolitionEffectiveDate, 2020-03-01]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fareAbolitionEffectiveDate Context triple: [Luxembourg national public transport system, fareAbolitionEffectiveDate, 2020-03-01]
-
A.
dateAbolished
Indicates the date on which something (such as an institution, law, practice, or position) was officially ended or abolished.
-
B.
farePolicyChangeDate
chosen
Indicates the date on which a fare policy is changed or becomes effective.
-
C.
tollAbolishedOn
Indicates that a previously existing toll was officially removed or discontinued on a specified date or event.
-
D.
repealEffectiveIn
Indicates that a repeal of a law, rule, or regulation becomes legally operative within a specified jurisdiction or context.
-
E.
officeAbolitionEffectiveDate
Indicates the date on which a particular office or position is formally abolished and ceases to exist.
- 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_69f76ef64cf08190ad3e1114b62aac67 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc7b78f9481909f4f8fc2e3fdcde1 |
completed | May 6, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69fbbd18c9908190928d274f8731dfa8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:20 p.m.