Triple
T1764549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Secretary of the Hanoi Party Committee |
E38731
|
entity |
| Predicate | scopeOfPower |
P31477
|
FINISHED |
| Object | city-wide |
—
|
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: city-wide | Statement: [Secretary of the Hanoi Party Committee, scopeOfPower, city-wide]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scopeOfPower Context triple: [Secretary of the Hanoi Party Committee, scopeOfPower, city-wide]
-
A.
powers
Indicates that one entity supplies or provides the energy, authority, or driving force that enables another entity to function or operate.
-
B.
exerciseOfPower
Indicates the exertion or application of authority, control, or influence by one entity over another or within a given context.
-
C.
exercisedPowerOver
Indicates that one entity exerted control, influence, or authority over another entity.
-
D.
powerStructure
Indicates how authority, control, and decision-making are distributed and organized among entities within a system or group.
-
E.
majorPowerIn
Indicates that an entity holds significant political, economic, or military influence within a specified domain, region, or context.
- 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_69a8862d562481908d7025a1c1f67c0d |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab173936b4819097332ee185996bbd |
completed | March 6, 2026, 6:04 p.m. |
| PD | Predicate disambiguation | batch_69aa61c9e06c819085489e00cfe72153 |
completed | March 6, 2026, 5:10 a.m. |
| PDg | Predicate description generation | batch_69ab173830a481908b67928f16f5d999 |
completed | March 6, 2026, 6:04 p.m. |
Created at: March 4, 2026, 7:31 p.m.