Triple
T17537123
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Official Languages Act of Nunavut |
E427089
|
entity |
| Predicate | collectiveTermUsed |
P127829
|
FINISHED |
| Object | Inuit Language |
—
|
LITERAL 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: Inuit Language | Statement: [Official Languages Act of Nunavut, collectiveTermUsed, Inuit Language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collectiveTermUsed Context triple: [Official Languages Act of Nunavut, collectiveTermUsed, Inuit Language]
-
A.
usedTerm
Indicates that one entity employed, referenced, or applied a particular term in some context.
-
B.
usedCollectiveName
Indicates that a group of entities is referred to by a shared collective name.
-
C.
commonCollocation
Indicates that two or more words frequently occur together in natural language usage as a typical or conventional combination.
-
D.
collectivelyKnownAs
Indicates that multiple entities are referred to together under a single shared name or designation.
-
E.
typicalTerm
Indicates that something is a standard, representative, or characteristic term typically associated with a given concept or context.
- F. None of above. chosen
Provenance (4 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_69d889de677081909b22d2657b1f0292 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e4536d03dc81908b8a58f66657c01a |
completed | April 19, 2026, 4 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f8b9888190aa8a45e09acf4319 |
completed | April 18, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69e3bbb37d148190b7f38599c06594ee |
completed | April 18, 2026, 5:13 p.m. |
Created at: April 10, 2026, 5:49 a.m.