Triple
T34995912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bakassi |
E1009526
|
entity |
| Predicate | formerlyClaimedBy |
P121269
|
FINISHED |
| Object | Nigeria |
—
|
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: Nigeria | Statement: [Bakassi, formerlyClaimedBy, Nigeria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerlyClaimedBy Context triple: [Bakassi, formerlyClaimedBy, Nigeria]
-
A.
alsoClaimedBy
Indicates that the same item, statement, or resource is asserted or claimed by an additional party besides the primary one.
-
B.
claimedAs
Indicates that one entity asserts ownership, authorship, responsibility, or some other form of association over another entity.
-
C.
alsoClaimedAs
Indicates that an entity is asserted to have an additional, alternative, or parallel claim or designation beyond its primary one.
-
D.
formerClaimant
chosen
Indicates that an entity previously held the status of claimant in a claim or dispute but no longer does so.
-
E.
historicallyClaimedBy
Indicates that an entity has, at some point in the past, asserted ownership, control, or rights over another entity or territory.
- 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_69f76dca50dc8190b71f39defe186be8 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a003f6083608190a5deadc7291cf70e |
completed | May 10, 2026, 8:18 a.m. |
| PD | Predicate disambiguation | batch_6a003c935c40819085fdb255a52ba03b |
completed | May 10, 2026, 8:06 a.m. |
Created at: May 3, 2026, 4:01 p.m.