Triple
T9033050
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chicago Skyway |
E216419
|
entity |
| Predicate | concessionLeaseStartDate |
P69608
|
FINISHED |
| Object | 2005 |
—
|
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: 2005 | Statement: [Chicago Skyway, concessionLeaseStartDate, 2005]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: concessionLeaseStartDate Context triple: [Chicago Skyway, concessionLeaseStartDate, 2005]
-
A.
leaseBegan
chosen
Indicates that a lease agreement between parties started or came into effect at a specific time.
-
B.
concessionYear
Indicates the year in which a concession, such as a right, license, or contract, was formally granted or came into effect.
-
C.
concessionExpiry
Indicates that a granted concession or special permission remains valid only until a specified expiration time or date.
-
D.
concessionDuration
Indicates the length of time for which a concession, such as a granted right or privilege, remains valid or in effect between parties.
-
E.
occupationDate
Indicates the date or time period during which an entity assumes, holds, or begins a particular role, position, or occupation.
- 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_69ca83d10b608190b2b2f8e0a7faaf14 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc6aa0c89c81909792190f08fef8df |
completed | April 1, 2026, 12:45 a.m. |
| PD | Predicate disambiguation | batch_69cc5ee3597c81908919cf866ae95c24 |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:08 p.m.