Triple
T31951183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mapuche communities of Wallmapu |
E815782
|
entity |
| Predicate | hasTraditionalAssembly |
P198389
|
FINISHED |
| Object | trawün |
—
|
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: trawün | Statement: [Mapuche communities of Wallmapu, hasTraditionalAssembly, trawün]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTraditionalAssembly Context triple: [Mapuche communities of Wallmapu, hasTraditionalAssembly, trawün]
-
A.
traditionalAssembly
Indicates that an entity is created, constructed, or put together using conventional, established methods rather than modern or alternative techniques.
-
B.
hasAssemblyLine
Indicates that one entity possesses or operates an assembly line used for producing or assembling items.
-
C.
hasTraditionalFormIn
Indicates that something possesses a customary or historically established form or representation within a specified context, system, or location.
-
D.
hasAssembly
Indicates that an entity is composed of, or includes, one or more component parts assembled into a whole.
-
E.
hasTraditionalBase
Indicates that something is supported by, built upon, or derived from an established traditional foundation or practice.
- 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_69f348f42d188190a33fc8d20ec50517 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fee0b2da3c8190a3519d0564f2f32d |
completed | May 9, 2026, 7:22 a.m. |
| PD | Predicate disambiguation | batch_69fee05b315c819081dfcbfb15273487 |
completed | May 9, 2026, 7:20 a.m. |
| PDg | Predicate description generation | batch_69fee0b03a0c81909117dc5915d77295 |
completed | May 9, 2026, 7:22 a.m. |
Created at: May 1, 2026, 12:07 a.m.