Triple
T23970
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New York City Subway |
E474
|
entity |
| Predicate | fareControl |
P1740
|
FINISHED |
| Object | turnstiles |
—
|
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: turnstiles | Statement: [New York City Subway, fareControl, turnstiles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fareControl Context triple: [New York City Subway, fareControl, turnstiles]
-
A.
fareSystem
Indicates a relationship where a system is used to determine, collect, or manage fares or payments for transportation or similar services.
-
B.
publicTransit
Indicates that one entity provides or is connected via shared, scheduled transportation services (such as buses, trains, or subways) that are available for use by the general public.
-
C.
hasFareZone
Indicates that an entity is located within or associated with a specific fare zone used for pricing or ticketing.
-
D.
governs
Indicates that one entity exercises authoritative control, direction, or rule over another entity or domain.
-
E.
requiresPermitFor
Indicates that one entity must obtain formal permission or authorization before performing an action involving another entity.
- 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_69a243b4ac2c8190b93c303df797b7b2 |
completed | Feb. 28, 2026, 1:24 a.m. |
| NER | Named-entity recognition | batch_69a246e94ca881908f7a7d2c0b293033 |
completed | Feb. 28, 2026, 1:37 a.m. |
| PD | Predicate disambiguation | batch_69a246560af88190961ea00b35cf9388 |
completed | Feb. 28, 2026, 1:35 a.m. |
| PDg | Predicate description generation | batch_69a246e7fac481909b0c500d4500650e |
completed | Feb. 28, 2026, 1:37 a.m. |
Created at: Feb. 28, 2026, 1:34 a.m.