Triple
T11267708
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hiệp Hòa District |
E266729
|
entity |
| Predicate | isPartOfCapitalRegionInfluenceArea |
P66890
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Hiệp Hòa District, isPartOfCapitalRegionInfluenceArea, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPartOfCapitalRegionInfluenceArea Context triple: [Hiệp Hòa District, isPartOfCapitalRegionInfluenceArea, true]
-
A.
isInStateCapitalRegionOf
Indicates that one entity is located within the capital region of the state to which the other entity belongs.
-
B.
locatedInNationCapitalRegion
chosen
Indicates that an entity is situated within the capital region of a specific nation.
-
C.
isRegionOf
Indicates that one entity is a geographic or administrative region belonging to, contained within, or associated with another entity.
-
D.
hasRegionalInfluenceFrom
Indicates that one entity’s influence, impact, or authority in a region is derived from or shaped by another entity.
-
E.
hasCapitalOfRepresentedArea
Indicates that an entity serves as the capital city or administrative center of the geographic or political area it represents.
- 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_69d6aac8c2f48190ad0596f1f89f0470 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e94f60d48190bc925c3cb88641a8 |
completed | April 9, 2026, 6 p.m. |
| PD | Predicate disambiguation | batch_69d7879bc56c8190b2e8d2193f29de05 |
completed | April 9, 2026, 11:03 a.m. |
Created at: April 8, 2026, 9:31 p.m.