Triple
T28733213
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kolety |
E730720
|
entity |
| Predicate | hasAboriginalNameFor |
P96958
|
FINISHED |
| Object | Edward River |
—
|
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: Edward River | Statement: [Kolety, hasAboriginalNameFor, Edward River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAboriginalNameFor Context triple: [Kolety, hasAboriginalNameFor, Edward River]
-
A.
indigenousNameOf
chosen
Indicates that one entity is the name used for another entity in an indigenous or native language.
-
B.
isIndigenousLanguageNameOf
Indicates that a given name is the name of a language as expressed in an indigenous language.
-
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.
hasNameInMi'kmaq
Indicates that an entity is known or referred to by a specific name in the Mi'kmaq language.
-
E.
hasEthnologueName
Indicates that an entity is associated with a specific language name as recorded in the Ethnologue reference.
- 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_69f043eae0908190b28ce314686247d7 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f65a6c900881908f18b61273d7bf8d |
completed | May 2, 2026, 8:11 p.m. |
| PD | Predicate disambiguation | batch_69f659ce58408190ba9e007b4810d4d0 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 5:59 a.m.