Triple
T31951034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | lonko |
E815778
|
entity |
| Predicate | locatedInCulture |
P97639
|
FINISHED |
| Object | Mapuche culture |
E1050245
|
NE 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: Mapuche culture | Statement: [lonko, locatedInCulture, Mapuche culture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInCulture Context triple: [lonko, locatedInCulture, Mapuche culture]
-
A.
basedInCulture
chosen
Indicates that an entity is situated within, originates from, or is fundamentally associated with a particular culture.
-
B.
positionOnCulture
Indicates the stance, viewpoint, or opinion that one entity holds regarding cultural issues, practices, or phenomena in relation to another entity or context.
-
C.
locatedIn
Indicates that one entity exists or is situated within the spatial, administrative, or conceptual boundaries of another entity.
-
D.
hasCulturalPresenceOf
Indicates that something exhibits, contains, or is characterized by the cultural influence, activities, or representation of a particular group, tradition, or culture.
-
E.
namedForCulturalRegion
Indicates that something is given a name derived from or honoring a specific cultural region.
- F. None of above.
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_69f348f42d188190a33fc8d20ec50517 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a01d7b3ce8c8190b2f90be730505765 |
completed | May 11, 2026, 1:20 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2e8a4bf8f881908d751241b633f64a |
completed | June 14, 2026, 11:02 a.m. |
| PD | Predicate disambiguation | batch_6a01d5115a6c8190a6d9f96ec484135a |
completed | May 11, 2026, 1:09 p.m. |
Created at: May 1, 2026, 12:07 a.m.