Triple
T2583683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ife Kingdom |
E57148
|
entity |
| Predicate | modernLocationCorrespondsTo |
P31256
|
FINISHED |
| Object | city of Ile-Ife in Osun State, Nigeria |
—
|
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: city of Ile-Ife in Osun State, Nigeria | Statement: [Ife Kingdom, modernLocationCorrespondsTo, city of Ile-Ife in Osun State, Nigeria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modernLocationCorrespondsTo Context triple: [Ife Kingdom, modernLocationCorrespondsTo, city of Ile-Ife in Osun State, Nigeria]
-
A.
presentDayLocationCorrespondsTo
chosen
Indicates that the current, real-world location of an entity matches or aligns with a specified reference location.
-
B.
refersToLocation
Indicates that one entity designates, points to, or identifies a specific location associated with it.
-
C.
mainLocation
Indicates that one entity serves as the primary or central location associated with another entity.
-
D.
leftLocation
Indicates that an entity has departed from or moved away from a specified location.
-
E.
coordinateLocation
Indicates that an entity is located at, or associated with, a specific geographic coordinate or set of coordinates.
- 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_69ab4a4dca6481908c301f8e317396e7 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd3cb33a08190a3eae1a95e1b63bf |
completed | March 7, 2026, 7:29 a.m. |
| PD | Predicate disambiguation | batch_69abd0cfeae08190aed03866ba071c5c |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:49 p.m.