Triple
T30113165
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lianghe |
E765340
|
entity |
| Predicate | hasAutonomousPrefectureContext |
P180444
|
FINISHED |
| Object | Dai ethnic group |
—
|
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: Dai ethnic group | Statement: [Lianghe, hasAutonomousPrefectureContext, Dai ethnic group]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAutonomousPrefectureContext Context triple: [Lianghe, hasAutonomousPrefectureContext, Dai ethnic group]
-
A.
hasPrefecture
Indicates that one administrative region or country possesses or is associated with a specific prefecture as a subordinate territorial unit.
-
B.
isPrefectureOfItself
Indicates that an administrative unit is considered a prefecture in its own right, rather than being part of another prefecture.
-
C.
isPrefecture
Indicates that one entity functions as an administrative prefecture governing or representing the other entity.
-
D.
hasPrefecturalCapitalFunction
Indicates that an entity serves as the administrative capital or main governmental center of a prefecture.
-
E.
hasPrefecturalOffice
Indicates that a given location or administrative unit contains or hosts an official prefectural government office.
- 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_69f22475ad7c8190be7f9541044a0bbb |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f74062b9388190b30546cf700a825c |
completed | May 3, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69f73c802b848190b61a416b7488bd96 |
completed | May 3, 2026, 12:16 p.m. |
| PDg | Predicate description generation | batch_69f74061c440819080434155c2d60341 |
completed | May 3, 2026, 12:32 p.m. |
Created at: April 29, 2026, 7:11 p.m.