Triple
T530967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beijing Subway |
E12220
|
entity |
| Predicate | hasLine |
P35
|
FINISHED |
| Object |
Line 16
Line 16 is a rapid transit line of the Beijing Subway system serving parts of the city with modern, high-capacity metro service.
|
E69576
|
NE FINISHED |
How this triple was built (4 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: Line 16 | Statement: [Beijing Subway, hasLine, Line 16]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Line 16 Context triple: [Beijing Subway, hasLine, Line 16]
-
A.
Line 15
Line 15 is a rapid transit line of the Beijing Subway system serving northern parts of the city with both urban and suburban stations.
-
B.
Line 14
Line 14 is a major rapid transit line of the Beijing Subway system that serves multiple key residential and commercial districts across the city.
-
C.
Line 13
Line 13 is a suburban loop line of the Beijing Subway that serves the northern part of the city and connects several major transfer stations.
-
D.
Line 10
Line 10 is a major loop line of the Beijing Subway that encircles central urban districts and serves as a key transfer route in the network.
-
E.
Line 9
Line 9 is a rapid transit line of the Beijing Subway system that serves as part of the city's urban rail network.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Line 16 Triple: [Beijing Subway, hasLine, Line 16]
Generated description
Line 16 is a rapid transit line of the Beijing Subway system serving parts of the city with modern, high-capacity metro service.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Line 16 Target entity description: Line 16 is a rapid transit line of the Beijing Subway system serving parts of the city with modern, high-capacity metro service.
-
A.
Line 15
Line 15 is a rapid transit line of the Beijing Subway system serving northern parts of the city with both urban and suburban stations.
-
B.
Line 14
Line 14 is a major rapid transit line of the Beijing Subway system that serves multiple key residential and commercial districts across the city.
-
C.
Line 13
Line 13 is a suburban loop line of the Beijing Subway that serves the northern part of the city and connects several major transfer stations.
-
D.
Line 10
Line 10 is a major loop line of the Beijing Subway that encircles central urban districts and serves as a key transfer route in the network.
-
E.
Line 9
Line 9 is a rapid transit line of the Beijing Subway system that serves as part of the city's urban rail network.
- F. None of above. chosen
Provenance (5 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_69a4933208e88190891f5debab1b776d |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a494dda58c8190870305056838a2b2 |
completed | March 1, 2026, 7:34 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a4e62e2b3c81908215dab8c0717495 |
completed | March 2, 2026, 1:21 a.m. |
| NEDg | Description generation | batch_69a4e6b3f570819087fe28f3225afe88 |
completed | March 2, 2026, 1:24 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69a4e706d3e88190822eeb4a724a9b6a |
completed | March 2, 2026, 1:25 a.m. |
Created at: March 1, 2026, 7:32 p.m.