Triple
T9991294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hanoi Party Committee |
E196891
|
entity |
| Predicate | politicalSystemLevel |
P15721
|
FINISHED |
| Object | municipal level |
—
|
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: municipal level | Statement: [Hanoi Party Committee, politicalSystemLevel, municipal level]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: politicalSystemLevel Context triple: [Hanoi Party Committee, politicalSystemLevel, municipal level]
-
A.
politicalSphere
Indicates involvement or relevance within the domain of politics, governance, or public policy activities and interactions.
-
B.
politicalForm
chosen
Indicates the type or structure of governance or political organization that characterizes an entity.
-
C.
powerClassification
Indicates how an entity’s power, strength, or influence is categorized or ranked within a defined system.
-
D.
politicalSystemOnOtherSide
Indicates that one political system is located or operates on the opposite side of a specified reference point or boundary relative to another.
-
E.
governsInPoliticalSystem
Indicates that one entity exercises authoritative control or rule over another entity within a specified political system or structure.
- 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_69ca82f1678c819093d06320a05f16a4 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdcb95842c8190b8cdce9584f19840 |
completed | April 2, 2026, 1:51 a.m. |
| PD | Predicate disambiguation | batch_69cd1da07db88190945bcdab3ca82e71 |
completed | April 1, 2026, 1:29 p.m. |
Created at: March 30, 2026, 8:50 p.m.