Triple
T14253137
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FRELIMO |
E353318
|
entity |
| Predicate | governedAsSinglePartyState |
P50915
|
FINISHED |
| Object | 1975–1990 |
—
|
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: 1975–1990 | Statement: [FRELIMO, governedAsSinglePartyState, 1975–1990]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governedAsSinglePartyState Context triple: [FRELIMO, governedAsSinglePartyState, 1975–1990]
-
A.
stateOfGovernorship
Indicates the relationship in which an individual holds or held the official position and authority of governor over a specific jurisdiction.
-
B.
stateParty
Indicates that an entity is a member or signatory state formally bound by a particular treaty, agreement, or convention.
-
C.
participatingState
Indicates that a state is taking part in, or is formally involved as a participant in, a specified event, process, or arrangement.
-
D.
representedState
Indicates that one entity serves as a representation or depiction of the state or condition of another entity.
-
E.
governsInPoliticalSystem
chosen
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_69d8278c43e08190824146f4632b89a5 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de6297f38c819090d7c7fd8bfa2e9e |
completed | April 14, 2026, 3:51 p.m. |
| PD | Predicate disambiguation | batch_69de05c09b7881908acbca18bd7d997c |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 1:09 a.m.