Triple
T32305655
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Juaneño |
E825355
|
entity |
| Predicate | endonymRelatedTo |
P94990
|
FINISHED |
| Object | Acjachemen |
—
|
NE NERFINISHED |
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: Acjachemen | Statement: [Juaneño, endonymRelatedTo, Acjachemen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endonymRelatedTo Context triple: [Juaneño, endonymRelatedTo, Acjachemen]
-
A.
hasEndonym
Indicates that an entity has a name or designation used by native speakers or within its own local language or community.
-
B.
isEndonym
chosen
Indicates that a name is used by a group to refer to themselves or their own place/language, rather than being an external or foreign designation.
-
C.
hasNameEtymologyIn
Indicates that the origin or derivation of an entity’s name is based in, or traceable to, a specified source such as a language, place, or cultural context.
-
D.
relatedEthnonymNote
Indicates that there is an explanatory note describing how this ethnonym is related to another ethnonym or term.
-
E.
hasLanguageOfToponym
Indicates that a place name (toponym) is expressed in or associated with a particular language.
- 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_69f349115304819084ee91d345b6c8aa |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bd81235081908c0748dfd5db5039 |
completed | May 3, 2026, 3:14 a.m. |
| PD | Predicate disambiguation | batch_69f6b632cf788190a3d0c08cd026b84b |
completed | May 3, 2026, 2:42 a.m. |
Created at: May 1, 2026, 12:45 a.m.