Triple
T10184668
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eritrean People's Liberation Front |
E236876
|
entity |
| Predicate | emphasizedPolicy |
P83753
|
FINISHED |
| Object | self-reliance |
—
|
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: self-reliance | Statement: [Eritrean People's Liberation Front, emphasizedPolicy, self-reliance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: emphasizedPolicy Context triple: [Eritrean People's Liberation Front, emphasizedPolicy, self-reliance]
-
A.
emphasizesPolicyArea
chosen
Indicates that one entity gives particular importance or priority to a specific policy area in its actions, statements, or focus.
-
B.
advancedPolicyOf
Indicates that one policy is a more developed, detailed, or progressive version of another policy.
-
C.
positionEmphasized
Indicates that a particular position, stance, or role is given special prominence or stress relative to others.
-
D.
strategyEmphasis
Indicates an entity’s primary focus or priority within a broader strategy or plan.
-
E.
governingPolicy
Indicates that one entity serves as the authoritative policy or set of rules that directs, constrains, or regulates the behavior, operation, or decisions of another entity.
- 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_69ca84d7260c8190bfbec36762943f37 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cded3566f881909e0d1366f501d554 |
completed | April 2, 2026, 4:14 a.m. |
| PD | Predicate disambiguation | batch_69cd7c79f21c8190a7f31b2eab80b8ba |
completed | April 1, 2026, 8:13 p.m. |
Created at: March 30, 2026, 9:12 p.m.