Triple
T3263730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fangshan Line |
E68472
|
entity |
| Predicate | isUrbanRailTransit |
P32065
|
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: [Fangshan Line, isUrbanRailTransit, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isUrbanRailTransit Context triple: [Fangshan Line, isUrbanRailTransit, yes]
-
A.
isPublicTransport
Indicates that the entity functions as a mode or instance of transportation that is available for use by the general public, typically operating on fixed routes or schedules.
-
B.
rapidTransitSystem
chosen
Indicates a transportation relationship where people or goods are moved via a high-capacity, high-frequency public transit system designed for rapid travel over urban or regional routes.
-
C.
hasLightRailSystem
Indicates that a place possesses and operates a light rail transit system.
-
D.
hasTramway
Indicates that a location or area is served by, contains, or is connected to a tramway system.
-
E.
appliesToTransitSystem
Indicates that something (such as a rule, policy, feature, or condition) is relevant or applicable to a particular transit or transportation system.
- 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_69ad8590444081909e8107a8aeef3a23 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adafaa35e48190b894ca41dd65932b |
completed | March 8, 2026, 5:19 p.m. |
| PD | Predicate disambiguation | batch_69ada41d7eac8190ada4bf5f793d5c49 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:09 p.m.