Triple
T75494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sinti |
E1508
|
entity |
| Predicate | culturalTrait |
P1114
|
FINISHED |
| Object | oral tradition |
—
|
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: oral tradition | Statement: [Sinti, culturalTrait, oral tradition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: culturalTrait Context triple: [Sinti, culturalTrait, oral tradition]
-
A.
culturalTradition
chosen
Indicates a relationship where certain practices, beliefs, or customs are recognized as part of a shared cultural heritage passed down within a group or society.
-
B.
hasCulturalFeature
Indicates that an entity possesses, includes, or is characterized by a particular cultural element, attribute, or landmark.
-
C.
hasCulturalSignificanceFor
Indicates that something holds particular cultural meaning, value, or importance for a specified group or community.
-
D.
hasCulturalSignificance
Indicates that something holds notable meaning, value, or importance within a particular culture or cultural context.
-
E.
culturalRegion
Indicates that an entity is located in, associated with, or belongs to a specific cultural region or cultural area.
- 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_69a24c60d19c8190a1b6c105ca59ef5b |
completed | Feb. 28, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69a25314bd6c81908d1cfd4b83f20049 |
completed | Feb. 28, 2026, 2:29 a.m. |
| PD | Predicate disambiguation | batch_69a24eae77ec81909015906f31f2b62e |
completed | Feb. 28, 2026, 2:10 a.m. |
Created at: Feb. 28, 2026, 2:06 a.m.