Triple
T19325052
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dien Bien province |
E483324
|
entity |
| Predicate | hasAdministrativeUnits |
P3892
|
FINISHED |
| Object | districts |
—
|
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: districts | Statement: [Dien Bien province, hasAdministrativeUnits, districts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAdministrativeUnits Context triple: [Dien Bien province, hasAdministrativeUnits, districts]
-
A.
hasAdministrativeUnit
chosen
Indicates that one entity possesses, contains, or is associated with another entity that functions as its administrative subdivision or governing unit.
-
B.
isAdministrativeUnit
Indicates that one entity functions as an official administrative division or unit within the governance or organizational structure of another entity.
-
C.
isAdministrativeUnitWithin
Indicates that one administrative unit is geographically or jurisdictionally contained within another administrative unit.
-
D.
usedAsAdministrativeUnit
Indicates that an entity functions as an official administrative unit within a governance or organizational structure.
-
E.
separatesAdministrativeUnits
Indicates that one entity serves as a boundary or divider that distinguishes or splits different administrative units from each other.
- 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_69d8e8d13e3c81909d91d1d5ec37c095 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e60d8af43c81908e5a8780c35a8e1d |
completed | April 20, 2026, 11:27 a.m. |
| PD | Predicate disambiguation | batch_69e4dd0ef66881909d489d634eee817a |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:32 p.m.