Triple
T37666617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kintango |
E937833
|
entity |
| Predicate | ethnicOrCulturalBackgroundInStory |
P150885
|
FINISHED |
| Object | Mandinka |
—
|
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: Mandinka | Statement: [Kintango, ethnicOrCulturalBackgroundInStory, Mandinka]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ethnicOrCulturalBackgroundInStory Context triple: [Kintango, ethnicOrCulturalBackgroundInStory, Mandinka]
-
A.
cultureOfOrigin
Indicates the cultural background or tradition from which an entity originates or is derived.
-
B.
nationalityInStory
Indicates that a character or entity in a narrative is associated with a particular nationality within the context of that story.
-
C.
ethnicOrigin
Indicates the relationship where an entity is associated with a particular ethnic group or ancestry.
-
D.
raceOfOrigin
Indicates the racial or ethnic group from which an entity originally comes or is derived.
-
E.
ethnicOrCulturalGroup
chosen
Indicates that one entity belongs to, is associated with, or is characterized by a particular ethnic or cultural group represented by the other entity.
- 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd57ba740c8190bd1d40166fccccb7 |
completed | May 8, 2026, 3:25 a.m. |
| PD | Predicate disambiguation | batch_69fd55ee82b881908a639da3a41b3af6 |
completed | May 8, 2026, 3:18 a.m. |
Created at: May 3, 2026, 4:18 p.m.