Triple
T37865669
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ndeʼ |
E944462
|
entity |
| Predicate | usedAsSelfDesignationFor |
P90351
|
FINISHED |
| Object | Chiricahua Apache community |
—
|
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: Chiricahua Apache community | Statement: [Ndeʼ, usedAsSelfDesignationFor, Chiricahua Apache community]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsSelfDesignationFor Context triple: [Ndeʼ, usedAsSelfDesignationFor, Chiricahua Apache community]
-
A.
usedAsSelfDesignation
Indicates that an entity is used by a person or group as a term to refer to or identify themselves.
-
B.
usesServiceDesignation
Indicates that one entity adopts or applies a particular service designation associated with another entity or offering.
-
C.
designationUsedFor
Indicates that a particular name, label, or title is employed to refer to or identify a specific entity or role.
-
D.
usesEthnonymForSelfDesignation
chosen
Indicates that an entity refers to itself using an ethnonym (a name of an ethnic group) as its own self-designation.
-
E.
usesDesignator
Indicates that one entity employs or references a specific designator (such as a name, code, or identifier) to denote or refer to another entity.
- 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_69f76eee2f9c8190b1272aa2ee55ebf5 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69ff17be6ad48190963206f2619b1b28 |
completed | May 9, 2026, 11:17 a.m. |
| PD | Predicate disambiguation | batch_69ff1724ba24819092c928fcbcb286ec |
completed | May 9, 2026, 11:14 a.m. |
Created at: May 3, 2026, 4:19 p.m.