Triple
T16456727
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Onöñda’gega’ |
E399701
|
entity |
| Predicate | culturalIdentifier |
P122854
|
FINISHED |
| Object | people of the hills |
—
|
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: people of the hills | Statement: [Onöñda’gega’, culturalIdentifier, people of the hills]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: culturalIdentifier Context triple: [Onöñda’gega’, culturalIdentifier, people of the hills]
-
A.
culturalRegister
Indicates the level or type of formality, style, or social context in which language or behavior is used or appropriate.
-
B.
culturalType
Indicates the classification of something according to its cultural category, style, or tradition.
-
C.
culturalRegion
Indicates that an entity is located in, associated with, or belongs to a specific cultural region or cultural area.
-
D.
culturalCategory
Indicates that one entity classifies or groups another entity according to a particular culture, tradition, or culturally defined type.
-
E.
hasCulturalIcon
Indicates that an entity is associated with or possesses a person, symbol, or object widely recognized as a significant representation of a particular culture.
- 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_69d87f2dac988190b74d6e185fa88ba4 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e32d7dfd188190b03e9b4151a4d3d8 |
completed | April 18, 2026, 7:06 a.m. |
| PD | Predicate disambiguation | batch_69e227048d608190a4205eae3117629a |
completed | April 17, 2026, 12:26 p.m. |
| PDg | Predicate description generation | batch_69e24556c1348190902a4d116c3137d9 |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 10, 2026, 5:10 a.m.