Triple
T17998961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pace Route 424 Linden CTA/Northbrook Court |
E430573
|
entity |
| Predicate | hasAlightingPolicy |
P85720
|
FINISHED |
| Object | front-door alighting |
—
|
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: front-door alighting | Statement: [Pace Route 424 Linden CTA/Northbrook Court, hasAlightingPolicy, front-door alighting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAlightingPolicy Context triple: [Pace Route 424 Linden CTA/Northbrook Court, hasAlightingPolicy, front-door alighting]
-
A.
hasLandingConditions
Indicates the specific conditions or requirements that must be met for a landing to occur or be permitted.
-
B.
passengerPolicy
chosen
Indicates the rules or conditions governing whether and how passengers are allowed or managed in a given context.
-
C.
hasBoardingOption
Indicates that an entity offers or is associated with a particular way or method by which passengers or items can board or be taken on.
-
D.
allowsUphillTravelPolicies
Indicates that a system or entity permits policies that enable or regulate travel in an uphill direction.
-
E.
hasLockFlight
Indicates that one entity is associated with a specific lock flight, representing a relationship where the entity uses, contains, or is located at that sequence of canal locks.
- 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_69d8b90364248190a37381adea932f42 |
completed | April 10, 2026, 8:46 a.m. |
| NER | Named-entity recognition | batch_69e4b3e6a2a881908af2d0a4a5053916 |
completed | April 19, 2026, 10:52 a.m. |
| PD | Predicate disambiguation | batch_69e3f90039e4819080527f860dca042e |
completed | April 18, 2026, 9:34 p.m. |
Created at: April 10, 2026, 10:23 a.m.