Triple
T24738971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trio people |
E618494
|
entity |
| Predicate | hasOralCulture |
P32654
|
FINISHED |
| Object | myths |
—
|
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: myths | Statement: [Trio people, hasOralCulture, myths]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOralCulture Context triple: [Trio people, hasOralCulture, myths]
-
A.
hasRichOralTradition
chosen
Indicates that an entity is associated with a longstanding, culturally significant body of stories, histories, or knowledge transmitted primarily through spoken word rather than written texts.
-
B.
hasCulturalExpression
Indicates that an entity embodies, manifests, or is associated with a particular cultural form, practice, or expression.
-
C.
hasCulturalFeature
Indicates that an entity possesses, includes, or is characterized by a particular cultural element, attribute, or landmark.
-
D.
hasCulturalOrientation
Indicates a relationship where an entity is associated with, aligned to, or characterized by a particular cultural background, perspective, or set of cultural norms.
-
E.
hasOratory
Indicates that one entity possesses or is characterized by skill or ability in public speaking or formal speech.
- 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_69e2fab8f95c81908bb9e552cf3280c2 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f464b4c9b0819085daa00c7c3b8b76 |
completed | May 1, 2026, 8:30 a.m. |
| PD | Predicate disambiguation | batch_69f45cf017a88190b4985b11159c907d |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 18, 2026, 4:04 a.m.