Triple

T3696970
Position Surface form Disambiguated ID Type / Status
Subject Guanggu E78481 entity
Predicate hasTransportConnection P845 FINISHED
Object Wuhan Metro network E11197 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: Wuhan Metro network | Statement: [Guanggu, hasTransportConnection, Wuhan Metro network]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Wuhan Metro network
Context triple: [Guanggu, hasTransportConnection, Wuhan Metro network]
  • A. Wuhan Metro chosen
    Wuhan Metro is the rapid transit system serving the city of Wuhan, China, providing urban rail transportation across its major districts.
  • B. Wuhan Metro Line 10
    Wuhan Metro Line 10 is a rapid transit line in Wuhan, China, forming part of the city's expanding urban subway network.
  • C. Wuhan Metro Line 28
    Wuhan Metro Line 28 is a planned rapid transit line intended to expand and improve the urban rail network in Wuhan, China.
  • D. Wuhan Metro Line 11
    Wuhan Metro Line 11 is a rapid transit line in Wuhan, China, serving as part of the city's expanding urban rail network.
  • E. Wuhan Metro Line 21
    Wuhan Metro Line 21 is a rapid transit line in Wuhan, China, serving as part of the city's expanding urban rail network.
  • 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_69ad85e3b1888190abc983e06968696d completed March 8, 2026, 2:21 p.m.
NER Named-entity recognition batch_69adc5115ad8819085ffa938de3943f4 completed March 8, 2026, 6:50 p.m.
NED1 Entity disambiguation (via context triple) batch_69b4cdf1b16081909b18af630d0b4817 completed March 14, 2026, 2:54 a.m.
Created at: March 8, 2026, 3:26 p.m.