Triple
T28106854
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hanzhong Road station |
E710386
|
entity |
| Predicate | fareControlledArea |
P8430
|
FINISHED |
| Object | paid transfer corridors |
—
|
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: paid transfer corridors | Statement: [Hanzhong Road station, fareControlledArea, paid transfer corridors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fareControlledArea Context triple: [Hanzhong Road station, fareControlledArea, paid transfer corridors]
-
A.
fareControlAreaLocatedIn
Indicates that a fare control area (e.g., turnstiles or ticket gates) is physically located within a specified larger facility or space.
-
B.
fareControlLocation
chosen
Indicates a location where access to or use of a transportation service is regulated, checked, or controlled for fare payment.
-
C.
fareControl
Indicates that an entity is responsible for monitoring, enforcing, or managing payment of fares for access to a service or facility.
-
D.
regulatedArea
Indicates that an area is subject to specific rules, controls, or restrictions imposed by an authority.
-
E.
fareZoneAuthority
Indicates that an authority or organization is responsible for defining, managing, or overseeing a specific fare zone.
- 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_69ef9b71fdb081908b4a61cd7ff147c1 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f640c50dc88190a93952b9b87eb588 |
completed | May 2, 2026, 6:21 p.m. |
| PD | Predicate disambiguation | batch_69f63c6a8474819091b8c6fe98e3862d |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 9:08 p.m.