Triple
T19334969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 23rd Street station (IND Sixth Avenue Line) |
E483597
|
entity |
| Predicate | hasFareControlAreaCount |
P135461
|
FINISHED |
| Object | multiple |
—
|
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: multiple | Statement: [23rd Street station (IND Sixth Avenue Line), hasFareControlAreaCount, multiple]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFareControlAreaCount Context triple: [23rd Street station (IND Sixth Avenue Line), hasFareControlAreaCount, multiple]
-
A.
hasFareControlLevel
Indicates the degree or type of access control applied to a transit facility or area for fare payment and validation.
-
B.
hasFareZoneSystem
Indicates that an entity uses or is associated with a particular fare zone system for determining travel costs or ticketing.
-
C.
hasFareZone
Indicates that an entity is located within or associated with a specific fare zone used for pricing or ticketing.
-
D.
hasFareZoneCode
Indicates that an entity is associated with a specific fare zone identifier used for pricing or tariff purposes.
-
E.
hasFareZoneFeature
Indicates that an entity is associated with a specific fare zone or fare-related area designation.
- 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_69d8e8d13e3c81909d91d1d5ec37c095 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e61644b80c819080f9bca086424a36 |
completed | April 20, 2026, 12:04 p.m. |
| PD | Predicate disambiguation | batch_69e4dd12303c8190a2027c062b2dff40 |
completed | April 19, 2026, 1:48 p.m. |
| PDg | Predicate description generation | batch_69e4df51ac6c819091ce72b07790ffa6 |
completed | April 19, 2026, 1:57 p.m. |
Created at: April 10, 2026, 1:33 p.m.