Triple
T3263738
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fangshan Line |
E68472
|
entity |
| Predicate | isDoubleTrack |
P16835
|
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, isDoubleTrack, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isDoubleTrack Context triple: [Fangshan Line, isDoubleTrack, yes]
-
A.
hasExpressTracks
Indicates that a transportation route or facility includes tracks designated for express service, allowing faster travel with fewer stops than regular tracks.
-
B.
railTracks
chosen
Indicates that one entity consists of, includes, or is associated with rail tracks used for guiding trains or rail vehicles.
-
C.
isElectricRailway
Indicates that a given railway system operates using electric power rather than diesel or other forms of propulsion.
-
D.
hasParallelTransit
Indicates that one transit route, service, or segment runs in parallel to another along a similar path or corridor.
-
E.
hasRackRailway
Indicates that one entity possesses or includes a rack railway system connecting locations or operating within its area.
- 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.