Triple

T8903768
Position Surface form Disambiguated ID Type / Status
Subject 蛇山 E211994 entity
Predicate 所属城市功能区 P37938 FINISHED
Object 武汉三镇之一武昌 LITERAL 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: 武汉三镇之一武昌 | Statement: [蛇山, 所属城市功能区, 武汉三镇之一武昌]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: 所属城市功能区
Context triple: [蛇山, 所属城市功能区, 武汉三镇之一武昌]
  • A. urbanAreaType
    Indicates the classification of an area based on its urban characteristics or development type (e.g., city, town, suburb, metropolitan region).
  • B. hasUrbanDistrictFunction
    Indicates that an entity serves the administrative or functional role of an urban district within a larger territorial or governance structure.
  • C. cityDistrictFunction
    Indicates that a specific function, role, or land-use purpose is assigned to or characterizes a particular district within a city.
  • D. regionOfCity chosen
    Indicates that a specified area or district is a constituent part or subdivision of a particular city.
  • E. urbanDistrictType
    Indicates the classification of an urban district according to its specific type or category within an administrative or planning system.
  • F. None of above.

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_69ca839255248190b43984294abd92ae completed March 30, 2026, 2:07 p.m.
NER Named-entity recognition batch_69cc64c2509881908fb692522d348e96 completed April 1, 2026, 12:20 a.m.
PD Predicate disambiguation batch_69cc5ecf55248190a29f00fbf99f13c4 completed March 31, 2026, 11:54 p.m.
Created at: March 30, 2026, 6:55 p.m.