Triple
T4035006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cowcaddens subway station |
E83806
|
entity |
| Predicate | hasAutomaticTicketGates |
P1973
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Cowcaddens subway station, hasAutomaticTicketGates, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAutomaticTicketGates Context triple: [Cowcaddens subway station, hasAutomaticTicketGates, yes]
-
A.
hasFaregates
chosen
Indicates that an entity is equipped with or contains faregates used to control or validate access, typically for paid entry.
-
B.
hasTicketInspection
Indicates that a ticket is checked or verified by an authorized inspector or system.
-
C.
hasAutomaticEntrance
Indicates that an entity is equipped with an entrance that operates automatically (e.g., opens or closes without manual effort).
-
D.
hasSelfServiceTicketMachines
Indicates that an entity is equipped with self-service ticket machines available for use.
-
E.
hasPlatformScreenDoors
Indicates that a transit station or platform is equipped with platform screen doors separating passengers from the tracks.
- 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_69aed92f7cf0819098e0539bdcc3767f |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefb11d92481909aaebbc250ff45b9 |
completed | March 9, 2026, 4:53 p.m. |
| PD | Predicate disambiguation | batch_69aef8fe440c819093a7fa22c4ff3f1a |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:36 p.m.