Triple
T34614340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sugluk Inlet |
E888821
|
entity |
| Predicate | hasNameInInuktitut |
P126318
|
FINISHED |
| Object | Sugluk |
—
|
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: Sugluk | Statement: [Sugluk Inlet, hasNameInInuktitut, Sugluk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNameInInuktitut Context triple: [Sugluk Inlet, hasNameInInuktitut, Sugluk]
-
A.
hasInuktitutName
chosen
Indicates that an entity has a name expressed in the Inuktitut language.
-
B.
hasInuktitutMeaning
Indicates that one entity serves as the Inuktitut-language meaning or translation of another entity.
-
C.
hasNameInAnishinaabemowin
Indicates that an entity is known by a particular name expressed in the Anishinaabemowin language.
-
D.
nameInYupikLanguages
Indicates that an entity has a specific name or designation when expressed in Yupik languages.
-
E.
hasNameInSakha
Indicates that an entity is associated with a specific name expressed in the Sakha (Yakut) 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_69f349d584e08190b40b9f6281ad50c4 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff16775a9881909d26dbc1f0ef3e1c |
completed | May 9, 2026, 11:11 a.m. |
| PD | Predicate disambiguation | batch_69ff158e61708190a1c581d0d306cfce |
completed | May 9, 2026, 11:07 a.m. |
Created at: May 1, 2026, 2:03 a.m.