Triple
T16958377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kolokuma Ijo |
E411362
|
entity |
| Predicate | isCulturalStandardFor |
P125388
|
FINISHED |
| Object | Ijo people |
—
|
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: Ijo people | Statement: [Kolokuma Ijo, isCulturalStandardFor, Ijo people]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCulturalStandardFor Context triple: [Kolokuma Ijo, isCulturalStandardFor, Ijo people]
-
A.
hasCulturalEquivalent
Indicates that one entity has a counterpart in another cultural context that plays a similar role, function, or meaning.
-
B.
hasCulturalScope
Indicates that a relationship or action is limited to, relevant within, or characterized by a particular cultural context or domain.
-
C.
basedInCulture
Indicates that an entity is situated within, originates from, or is fundamentally associated with a particular culture.
-
D.
isCulturalSignificance
Indicates that something holds notable meaning, value, or influence within a particular culture or cultural context.
-
E.
hasCulturalConcept
Indicates that an entity embodies, includes, or is associated with a particular cultural idea, value, practice, or construct.
- F. None of above. chosen
Provenance (4 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_69d886c9c9d481909afe222093641cae |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d01e420881909be1d93d7d6772fd |
completed | April 18, 2026, 6:40 p.m. |
| PD | Predicate disambiguation | batch_69e32b9aa8748190b248890aca86753d |
completed | April 18, 2026, 6:58 a.m. |
| PDg | Predicate description generation | batch_69e355722040819098830dabf207ecd6 |
completed | April 18, 2026, 9:57 a.m. |
Created at: April 10, 2026, 5:31 a.m.