Triple
T26601353
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | First Nations in Quebec |
E667641
|
entity |
| Predicate | hasPrimaryColonialLanguage |
P82461
|
FINISHED |
| Object | French |
—
|
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: French | Statement: [First Nations in Quebec, hasPrimaryColonialLanguage, French]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryColonialLanguage Context triple: [First Nations in Quebec, hasPrimaryColonialLanguage, French]
-
A.
hasColonialLanguage
Indicates that one entity uses or is associated with the colonial language historically imposed or introduced by another entity.
-
B.
languageOfColonialSettlers
chosen
Indicates the language historically spoken by colonial settlers in a given place or context.
-
C.
officialLanguageDuringColonialPeriod
Indicates that a language served as the official language of administration or governance in a territory during its colonial period.
-
D.
hasPrimaryVernacularLanguageFamily
Indicates that an entity’s main vernacular language belongs to a specified language family.
-
E.
hasPrimaryTraditionalLanguage
Indicates that one entity is the main or principal traditional language associated with 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_69ee9cfd20348190bb1255d2603efb7a |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69fd2cf39b0c8190811b8a6fa9410560 |
completed | May 8, 2026, 12:23 a.m. |
| PD | Predicate disambiguation | batch_69fd2ad8dd988190a9899701ba00d917 |
completed | May 8, 2026, 12:14 a.m. |
Created at: April 27, 2026, 2:12 a.m.