Triple
T38267037
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stockholm congestion tax |
E1021091
|
entity |
| Predicate | trialPeriodEndDate |
P63743
|
FINISHED |
| Object | 2006-07-31 |
—
|
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: 2006-07-31 | Statement: [Stockholm congestion tax, trialPeriodEndDate, 2006-07-31]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trialPeriodEndDate Context triple: [Stockholm congestion tax, trialPeriodEndDate, 2006-07-31]
-
A.
trialServiceEndDate
chosen
Indicates the date on which a trial service period ends.
-
B.
grantPeriodEnd
Indicates the date or point in time when a grant’s active period or eligibility officially ends.
-
C.
validityPeriodEnd
Indicates the date and time at which a previously valid state, authorization, or condition ceases to be valid.
-
D.
testingPeriod
Indicates a time-limited phase during which something is tried, evaluated, or assessed before a final decision or full implementation is made.
-
E.
typicalEndDate
Indicates the date on which something, such as an event, process, or period, normally or customarily ends.
- 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_69f76dee198c8190bf5109421e47a658 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fccbd826708190b5fab12c4236299a |
completed | May 7, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69fcc58838e08190b8fa54aa5c165f2d |
completed | May 7, 2026, 5:02 p.m. |
Created at: May 3, 2026, 4:30 p.m.