Triple
T6147648
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Binh Long Province |
E137118
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | former administrative province |
C536
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: former administrative province Context triple: [Binh Long Province, instanceOf, former administrative province]
-
A.
former administrative territorial entity
chosen
A former administrative territorial entity is a geographic area that once functioned as an official unit of government or administration but has since been dissolved, merged, or reorganized and no longer holds that status.
-
B.
former province of France
A former province of France is a historical territorial and administrative region that existed before the French Revolution, often retaining distinct cultural and regional identities despite no longer having official administrative status.
-
C.
historical province of Japan
A historical province of Japan is a former administrative and geographic division that existed before the modern prefecture system, often retaining cultural and historical significance in regional identity.
-
D.
former province of Finland
A former province of Finland is an administrative region that existed under Finland’s historical provincial system but has since been reorganized or abolished in later territorial reforms.
-
E.
former province of Italy
A former province of Italy is an obsolete administrative division that once functioned as a mid-level local government unit within an Italian region, typically encompassing multiple municipalities before being reorganized or replaced.
- F. None of above.
Provenance (1 batch)
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_69c008a2c6308190a56519b22d55d083 |
completed | March 22, 2026, 3:20 p.m. |
Created at: March 22, 2026, 4:16 p.m.