Triple
T15846519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guandu |
E384228
|
entity |
| Predicate | hasLandmark |
P105
|
FINISHED |
| Object | Guandu Bridge |
E380604
|
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: Guandu Bridge | Statement: [Guandu, hasLandmark, Guandu Bridge]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Guandu Bridge Context triple: [Guandu, hasLandmark, Guandu Bridge]
-
A.
Guandu Bridge
chosen
Guandu Bridge is a prominent red arch bridge in New Taipei City, Taiwan, known for carrying road traffic across the Tamsui River and serving as a local landmark.
-
B.
Zhongxiao Bridge
Zhongxiao Bridge is a major road bridge in Taipei, Taiwan, that spans the Tamsui River and connects key districts of the city.
-
C.
Chengmei Bridge
Chengmei Bridge is a notable road bridge spanning the Keelung River in Taipei, Taiwan, serving as an important local transportation link.
-
D.
Guomao Bridge
Guomao Bridge is a major multi-level traffic interchange in Beijing’s central business district, serving as a key junction for both road transport and nearby metro lines.
-
E.
Dazhi Bridge
Dazhi Bridge is a prominent arch bridge in Taipei, Taiwan, known for its distinctive illuminated design spanning the Keelung River.
- 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_69d86da422088190aac39e32e6c68429 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e14ca7c8f08190abe21cbb0c390f95 |
completed | April 16, 2026, 8:55 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffa143dcb48190951648edeae6542d |
completed | May 9, 2026, 9:04 p.m. |
Created at: April 10, 2026, 4:50 a.m.