Triple
T24138431
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saro people |
E598154
|
entity |
| Predicate | primarySettlementLocation |
P136244
|
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: [Saro people, primarySettlementLocation, Nigeria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primarySettlementLocation Context triple: [Saro people, primarySettlementLocation, Nigeria]
-
A.
primarySettlementOrigin
Indicates that one settlement is the main or original source from which another settlement was founded or developed.
-
B.
primaryTown
Indicates that a given town is the main or most important town associated with an entity (such as a person, organization, or region).
-
C.
mainSettlement
Indicates that one settlement serves as the primary or most important settlement associated with a given area, region, or administrative unit.
-
D.
primaryLocationCity
chosen
Indicates the city that serves as the main or primary location associated with the subject.
-
E.
mainSettlementLocatedOn
Indicates that the primary settlement of an area is situated on or directly adjacent to a specified geographic feature or location.
- 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_69e288c92e448190ac57034fa0c863ce |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1df7e3c20819099ff289789829d7e |
completed | April 29, 2026, 10:37 a.m. |
| PD | Predicate disambiguation | batch_69f1765650fc8190a6bc1eb512b240bf |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 11:27 p.m.