Triple
T34541319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nigerian military regime (1983–1993) |
E886813
|
entity |
| Predicate | liberalized |
P161195
|
FINISHED |
| Object | trade policy |
—
|
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: trade policy | Statement: [Nigerian military regime (1983–1993), liberalized, trade policy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: liberalized Context triple: [Nigerian military regime (1983–1993), liberalized, trade policy]
-
A.
emancipated
Indicates that one entity has been freed from the control, authority, or legal dependency of another.
-
B.
relinquished
Indicates that one entity voluntarily gave up possession, control, or claim over something to another entity or to no one.
-
C.
erlässt
Indicates that an authority issues, enacts, or promulgates something such as a law, decree, or regulation.
-
D.
lowered
chosen
Indicates that one entity caused another entity’s level, value, position, or intensity to become less than it was before.
-
E.
ally
Indicates a cooperative relationship in which one entity supports, assists, or aligns with another, often for mutual benefit or a shared goal.
- 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_69f349ce5eb881909e431c670944aa68 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71ff3ae60819089447abe3ff9e784 |
completed | May 3, 2026, 10:14 a.m. |
| PD | Predicate disambiguation | batch_69f71cc8074c81909ae09bea2acf1a09 |
completed | May 3, 2026, 10 a.m. |
Created at: May 1, 2026, 2:02 a.m.