Triple
T6362176
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Storyteller |
E143135
|
entity |
| Predicate | blends |
P47548
|
FINISHED |
| Object | traditional Indigenous oral narratives |
—
|
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: traditional Indigenous oral narratives | Statement: [Storyteller, blends, traditional Indigenous oral narratives]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: blends Context triple: [Storyteller, blends, traditional Indigenous oral narratives]
-
A.
usedInBlends
Indicates that something serves as an ingredient or component within one or more mixtures, combinations, or blends.
-
B.
mixesWith
Indicates that one entity is combined or blended together with another entity to form a mixture.
-
C.
typicalBlendStyle
Indicates the usual or characteristic way in which two or more elements are combined or mixed together.
-
D.
mixesElementsOf
chosen
Indicates a relationship where one entity combines or blends components, features, or aspects of another entity or set of entities into a unified whole.
-
E.
typicalBlendPartner
Indicates that two entities are commonly or characteristically combined or mixed together as standard or usual partners.
- 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_69c008d7a9c4819098d647ec47776917 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0680c02b481908618317566e31a5c |
completed | March 22, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69c060ec091c8190912aac44e1b8b1c9 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:32 p.m.