Triple
T9833271
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guangzhou BRT |
E239038
|
entity |
| Predicate | corridor |
P5520
|
FINISHED |
| Object | Tianhe Road |
E708875
|
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: Tianhe Road | Statement: [Guangzhou BRT, corridor, Tianhe Road]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Tianhe Road Context triple: [Guangzhou BRT, corridor, Tianhe Road]
-
A.
Tianhe Road
chosen
Tianhe Road is a major commercial and traffic artery in Guangzhou’s Tianhe District, lined with shopping centers, offices, and urban amenities.
-
B.
Changle Road
Changle Road is a historic, tree-lined street in Shanghai known for its European-style architecture, boutiques, and cafés dating back to the city’s colonial era.
-
C.
Zhongshan Avenue
Zhongshan Avenue is a major thoroughfare in Guangzhou, China, serving as one of the city’s key commercial and transportation corridors.
-
D.
Jianguo Road
Jianguo Road is a major thoroughfare in Beijing that forms part of the extended east–west urban axis associated with Chang’an Avenue.
-
E.
Hangzhong Road
Hangzhong Road is a Shanghai Metro station that serves as a terminus on a branch of Line 10 in Shanghai, China.
- 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_69ca84e314108190978324a4bdb959f8 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb336bfc4819084f0d4d6d1867484 |
completed | April 2, 2026, 12:07 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d1e423ba2c81909a46e56e2b004097 |
completed | April 5, 2026, 4:25 a.m. |
Created at: March 30, 2026, 8:32 p.m.