Triple
T9588309
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chi Đông Township |
E231348
|
entity |
| Predicate | hasCapitalOfLevel |
P89958
|
FINISHED |
| Object | local administrative center |
—
|
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: local administrative center | Statement: [Chi Đông Township, hasCapitalOfLevel, local administrative center]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCapitalOfLevel Context triple: [Chi Đông Township, hasCapitalOfLevel, local administrative center]
-
A.
hasCapitalCityOfContainingUnit
Indicates that a capital city belongs to and is located within a particular larger administrative or territorial unit.
-
B.
hasCapital
Indicates that a place or political entity has a specific city designated as its capital.
-
C.
hasCapitalOfRepresentedArea
Indicates that an entity serves as the capital city or administrative center of the geographic or political area it represents.
-
D.
containsCapitalOf
Indicates that one location geographically includes the city that serves as the capital of another region or entity.
-
E.
hasCapitalAdministered
Indicates that a specified capital city is responsible for administering or governing a particular territory or political entity.
- 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_69ca848161688190a68d514a0a9d5129 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd99f01ca08190afaa44645a58e918 |
completed | April 1, 2026, 10:19 p.m. |
| PD | Predicate disambiguation | batch_69ccd59fd7408190b36831902e3f37f7 |
completed | April 1, 2026, 8:21 a.m. |
| PDg | Predicate description generation | batch_69ccd93e90048190a2b0d7c5c195ba98 |
completed | April 1, 2026, 8:37 a.m. |
Created at: March 30, 2026, 8:06 p.m.