Triple
T37437671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mulao people |
E930322
|
entity |
| Predicate | autonomousCountyIn |
P187817
|
FINISHED |
| Object | Guangxi Zhuang Autonomous Region |
—
|
NE NERFINISHED |
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: Guangxi Zhuang Autonomous Region | Statement: [Mulao people, autonomousCountyIn, Guangxi Zhuang Autonomous Region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: autonomousCountyIn Context triple: [Mulao people, autonomousCountyIn, Guangxi Zhuang Autonomous Region]
-
A.
autonomousCounty
Indicates that a county possesses a degree of self-governance or political autonomy distinct from higher-level administrative authorities.
-
B.
isNamedCountyOf
Indicates that a county bears a specific official name within a given jurisdiction or context.
-
C.
inCounty
Indicates that one entity is geographically or administratively located within the boundaries of a specified county.
-
D.
inAutonomousCommunity
Indicates that one entity is located within or belongs administratively to a specific autonomous community.
-
E.
isInCountySeatOf
Indicates that one entity is located within the town or city that serves as the administrative center (county seat) of a specified county.
- F. None of above. chosen
Provenance (4 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_69f76ebfdcb8819098562ff3db673b04 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb92efc5948190a040ba2028bab964 |
completed | May 6, 2026, 7:13 p.m. |
| PD | Predicate disambiguation | batch_69fb8d0b52588190bb29937a43b99b5e |
completed | May 6, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69fb92ee27408190b0116ef2d789abac |
completed | May 6, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:17 p.m.