Triple
T35712428
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beijing–Xi'an high-speed rail corridor |
E1031899
|
entity |
| Predicate | integratesLine |
P1075
|
FINISHED |
| Object | Beijing–Zhengzhou high-speed railway |
—
|
NE NERFINISHED |
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: Beijing–Zhengzhou high-speed railway | Statement: [Beijing–Xi'an high-speed rail corridor, integratesLine, Beijing–Zhengzhou high-speed railway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: integratesLine Context triple: [Beijing–Xi'an high-speed rail corridor, integratesLine, Beijing–Zhengzhou high-speed railway]
-
A.
integrates
chosen
Indicates that one entity combines or brings together another entity or set of entities into a unified, functioning whole.
-
B.
integratesOn
Indicates that one entity is designed to work seamlessly within, or be combined functionally with, another entity or platform.
-
C.
connectedLine
Indicates that two entities are joined by a continuous line or linear connection.
-
D.
линия
Indicates a relationship where something is a line or forms a linear connection or boundary between points or areas.
-
E.
loopLine
Indicates that a line or path forms a closed loop, returning to its starting point without interruption.
- 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_69f76e0df1d08190965b1c6dff94c391 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a34f8ee08190a040304635539a8f |
completed | May 3, 2026, 7:34 p.m. |
| PD | Predicate disambiguation | batch_69f7a06f125c8190843af194f042a465 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:05 p.m.