Triple
T14037549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | President of MPLA |
E337750
|
entity |
| Predicate | hasPoliticalScope |
P38306
|
FINISHED |
| Object | national |
—
|
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: national | Statement: [President of MPLA, hasPoliticalScope, national]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPoliticalScope Context triple: [President of MPLA, hasPoliticalScope, national]
-
A.
hasPoliticalComponent
Indicates that something includes, involves, or is influenced by political factors, interests, or considerations.
-
B.
hasPoliticalOfficeScope
chosen
Indicates that a political office or position is limited to, defined within, or applicable to a specific jurisdiction, level, or scope of political authority.
-
C.
hasPolity
Indicates that one entity possesses, controls, or is associated with a particular political organization, governance structure, or state-like authority.
-
D.
hasPoliticalCharacteristic
Indicates that an entity possesses a specific political attribute, quality, or affiliation.
-
E.
geopoliticalScope
Indicates the geographic or political area within which an entity’s authority, relevance, or effect is defined or applies.
- 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_69d81c664e48819088cbd8f433aeffe5 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de30e312148190a6be0a3258364e6e |
completed | April 14, 2026, 12:19 p.m. |
| PD | Predicate disambiguation | batch_69de05ab36b48190920efb1869bdb1fe |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:20 p.m.