Triple
T29196764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Truong Dinh Ward |
E740145
|
entity |
| Predicate | isAdminUnitOf |
P63290
|
FINISHED |
| Object | Hanoi |
—
|
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: Hanoi | Statement: [Truong Dinh Ward, isAdminUnitOf, Hanoi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAdminUnitOf Context triple: [Truong Dinh Ward, isAdminUnitOf, Hanoi]
-
A.
authorizedUnit
Indicates that one entity is officially permitted or empowered to act on behalf of, or perform certain actions for, another entity or system.
-
B.
isAdministrativeUnit
Indicates that one entity functions as an official administrative division or unit within the governance or organizational structure of another entity.
-
C.
hasAdministrativeUnit
Indicates that one entity possesses, contains, or is associated with another entity that functions as its administrative subdivision or governing unit.
-
D.
isUnitIn
Indicates that a specific unit is located within or belongs to a particular container, group, or context.
-
E.
isAdministrativeUnitWithin
chosen
Indicates that one administrative unit is geographically or jurisdictionally contained within another administrative unit.
- 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_69f07cb8033c8190b8807e219a14333d |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f663c23e6c81909bfcf620e519017a |
completed | May 2, 2026, 8:51 p.m. |
| PD | Predicate disambiguation | batch_69f65c24f8b48190af81b575f3c15be5 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 12:04 p.m.