Triple
T38119051
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ibibio-Efik cluster |
E951879
|
entity |
| Predicate | minorPresenceIn |
P142188
|
FINISHED |
| Object | Rivers State |
—
|
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: Rivers State | Statement: [Ibibio-Efik cluster, minorPresenceIn, Rivers State]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: minorPresenceIn Context triple: [Ibibio-Efik cluster, minorPresenceIn, Rivers State]
-
A.
hasMinorPresenceIn
chosen
Indicates that an entity is present or active in a location, context, or domain, but only to a small or limited extent.
-
B.
minorSector
Indicates that one sector is a subordinate or less significant subdivision within a larger, primary sector.
-
C.
minorSignCategory
Indicates that one sign is classified as a minor or subordinate category within a broader system of sign types.
-
D.
isMinor
Indicates that one entity is legally or socially considered underage or not yet an adult in relation to a given context.
-
E.
minorProduction
Indicates that an entity is involved in a secondary or less significant production activity relative to a primary production process.
- 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_69f76f07734c8190814e937e12257a78 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fc4748843c8190931432653be4890c |
completed | May 7, 2026, 8:03 a.m. |
| PD | Predicate disambiguation | batch_69fc45646ce481908caf292ff9f06e15 |
completed | May 7, 2026, 7:55 a.m. |
Created at: May 3, 2026, 4:21 p.m.