Triple
T37830230
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Morris Park station |
E943178
|
entity |
| Predicate | hasFareControlEquipment |
P1973
|
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: [Morris Park station, hasFareControlEquipment, turnstiles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFareControlEquipment Context triple: [Morris Park station, hasFareControlEquipment, turnstiles]
-
A.
hasFareControlIntegrationSince
Indicates that a fare control system has been integrated with another system or entity starting from a specific point in time.
-
B.
hasFareControlLevel
Indicates the degree or type of access control applied to a transit facility or area for fare payment and validation.
-
C.
hasAutomaticFareCollection
Indicates that an entity is equipped with a system that automatically collects fares or payments from users without manual processing.
-
D.
hasFaregates
chosen
Indicates that an entity is equipped with or contains faregates used to control or validate access, typically for paid entry.
-
E.
hasFareIntegration
Indicates that two or more transportation services or systems share a coordinated fare structure, allowing passengers to use a single ticket or payment arrangement across them.
- 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_69f76eea4c8c8190a335aed5955cf2db |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fe9dfaa2d08190b2084f63f842eb6b |
completed | May 9, 2026, 2:37 a.m. |
| PD | Predicate disambiguation | batch_69fe9bba947c81908b0b2b92a4d19b37 |
completed | May 9, 2026, 2:28 a.m. |
Created at: May 3, 2026, 4:19 p.m.