Triple
T36615954
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northern Angola |
E903603
|
entity |
| Predicate | wasAreaOfActivityFor |
P7685
|
FINISHED |
| Object | MPLA |
—
|
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: MPLA | Statement: [Northern Angola, wasAreaOfActivityFor, MPLA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasAreaOfActivityFor Context triple: [Northern Angola, wasAreaOfActivityFor, MPLA]
-
A.
area of activity
Indicates the domain, field, or sphere in which an entity is active or carries out its primary functions or operations.
-
B.
historicallyActiveIn
chosen
Indicates that an entity was active or engaged in significant activities within a particular place or context during a past historical period.
-
C.
occupationOf
Indicates that one entity holds or performs the job, role, or profession associated with another entity.
-
D.
notableYearOfActivity
Indicates the specific year during which an entity was particularly active, prominent, or notable in its activities or impact.
-
E.
workedPrimarilyIn
Indicates that an entity carried out the majority of its work, activity, or career within a particular field, location, or context.
- 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_69f76e6960e4819092047756ceb9a17e |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c477a4d481908f52e55b6688f60c |
completed | May 3, 2026, 9:56 p.m. |
Created at: May 3, 2026, 4:11 p.m.