Triple
T21623184
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jongno 3-ga Station |
E533627
|
entity |
| Predicate | hasFareGateType |
P1973
|
FINISHED |
| Object | automatic fare collection gates |
—
|
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: automatic fare collection gates | Statement: [Jongno 3-ga Station, hasFareGateType, automatic fare collection gates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFareGateType Context triple: [Jongno 3-ga Station, hasFareGateType, automatic fare collection gates]
-
A.
hasFaregates
chosen
Indicates that an entity is equipped with or contains faregates used to control or validate access, typically for paid entry.
-
B.
hasFareGateConnectionTo
Indicates that there is a direct passage or connection between two areas that is controlled or mediated by fare gates.
-
C.
hasFareZoneSystem
Indicates that an entity uses or is associated with a particular fare zone system for determining travel costs or ticketing.
-
D.
hasFareControlLevel
Indicates the degree or type of access control applied to a transit facility or area for fare payment and validation.
-
E.
hasFareZoneFeature
Indicates that an entity is associated with a specific fare zone or fare-related area designation.
- 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_69e0c464fba881908d0ff2ac80511ce1 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef3bb0c42c8190997fbeb7a764d60e |
completed | April 27, 2026, 10:34 a.m. |
| PD | Predicate disambiguation | batch_69e69665fe8c8190af7e38785db188b2 |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:34 p.m.