Triple
T38150829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apsáalooke Reservation |
E952745
|
entity |
| Predicate | hasPrimaryEthnonymLanguage |
P207616
|
FINISHED |
| Object | Apsáalooke |
E284126
|
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: Apsáalooke | Statement: [Apsáalooke Reservation, hasPrimaryEthnonymLanguage, Apsáalooke]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryEthnonymLanguage Context triple: [Apsáalooke Reservation, hasPrimaryEthnonymLanguage, Apsáalooke]
-
A.
hasPrimaryEthnonym
Indicates that an entity is associated with its main or most commonly used ethnonym (ethnic group name) as its primary designation.
-
B.
hasPrimaryVernacularLanguageFamily
Indicates that an entity’s main vernacular language belongs to a specified language family.
-
C.
hasPrimaryLanguageForToponym
Indicates that a particular language is the main or official language used for the naming or labeling of a specific place name (toponym).
-
D.
hasEthnonymCountry
Indicates that an ethnonym (a name for an ethnic group or people) is associated with or pertains to a specific country.
-
E.
hasEthnologueName
Indicates that an entity is associated with a specific language name as recorded in the Ethnologue reference.
- F. None of above. chosen
Provenance (5 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_69f76f0a67f4819080c492f61d688fcc |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037df1223c8190a5d61e4f8e6fd613 |
completed | May 12, 2026, 7:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a42157c542c81909ae6b9b7ff1b3038 |
completed | June 29, 2026, 6:49 a.m. |
| PD | Predicate disambiguation | batch_6a037a1ad6c48190bfe35d350c1b4751 |
completed | May 12, 2026, 7:06 p.m. |
| PDg | Predicate description generation | batch_6a037df009f4819082e04683e6e8a106 |
completed | May 12, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:21 p.m.