Triple
T14628060
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neihu District |
E343403
|
entity |
| Predicate | isServedBy |
P1293
|
FINISHED |
| Object | Wenhu Line |
E377171
|
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: Wenhu Line | Statement: [Neihu District, isServedBy, Wenhu Line]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Wenhu Line Context triple: [Neihu District, isServedBy, Wenhu Line]
-
A.
Wenhu line
chosen
The Wenhu line is a driverless, medium-capacity rapid transit line in the Taipei Metro system that connects key districts across Taipei and New Taipei City.
-
B.
Yanfang Line
Yanfang Line is a suburban rapid transit line of the Beijing Subway serving the southwestern outskirts of the city.
-
C.
Yangluo Line
The Yangluo Line is a rapid transit line within the Wuhan Metro system serving the Yangluo area and connecting it to the broader urban network.
-
D.
Xijiao Line
The Xijiao Line is a light rail transit line in Beijing that primarily serves the city’s western suburban areas, including university and technology districts.
-
E.
Pujiang Line
The Pujiang Line is an automated, medium-capacity metro line serving the Pujiang area in Shanghai as part of the Shanghai Metro system.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d822dffc3c8190aa173b90761bffda |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb4a7c8fc81909d10c1f563d7d1e7 |
completed | April 14, 2026, 9:41 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fda92c25ac8190ba931c009e7ace19 |
completed | May 8, 2026, 9:13 a.m. |
Created at: April 10, 2026, 1:26 a.m.