Triple
T36077076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JGK |
E1043524
|
entity |
| Predicate | associatedWithHighSpeedLines |
P48478
|
FINISHED |
| Object | Beijing–Shanghai High-Speed Railway |
E222463
|
NE 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: Beijing–Shanghai High-Speed Railway | Statement: [JGK, associatedWithHighSpeedLines, Beijing–Shanghai High-Speed Railway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithHighSpeedLines Context triple: [JGK, associatedWithHighSpeedLines, Beijing–Shanghai High-Speed Railway]
-
A.
hasHighSpeedLine
chosen
Indicates that there exists a high-speed rail line connection between the related entities.
-
B.
hasHighSpeedSections
Indicates that the entity includes segments or portions where operation or movement occurs at high speed.
-
C.
notHighSpeedLine
Indicates that the line or connection does not qualify as a high-speed line according to the relevant criteria or standards.
-
D.
associatedWithTransitLine
Indicates that an entity has a connection or linkage to a specific transit line, such as being part of, served by, or otherwise related to that line.
-
E.
speedOfHighSpeedTrain
Indicates the velocity at which a high-speed train is traveling.
- F. None of above.
Provenance (4 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_69f76e3154908190a6f702671c2bea08 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a38d53e8dfc819095ae213a57f4b030 |
completed | June 22, 2026, 6:25 a.m. |
| PD | Predicate disambiguation | batch_6a037a0895b48190acdd88dc10db7be7 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:08 p.m.