Triple
T21911531
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Montreal (1844–1849) |
E541075
|
entity |
| Predicate | hasLanguageOfGovernment |
P112296
|
FINISHED |
| Object | English |
—
|
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: English | Statement: [Montreal (1844–1849), hasLanguageOfGovernment, English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLanguageOfGovernment Context triple: [Montreal (1844–1849), hasLanguageOfGovernment, English]
-
A.
hasLanguageOfOfficialName
Indicates that an entity’s official name is expressed in a specified language.
-
B.
hasOfficialCountryLanguage
Indicates that a country recognizes a particular language as one of its official languages for governmental or legal purposes.
-
C.
hasLanguageOfficial
chosen
Indicates that a language holds official status within a given entity, such as a country, region, or organization.
-
D.
hasNotableLanguageWithOfficialStatusIn
Indicates that a language holds an officially recognized and notable status within a specified jurisdiction or region.
-
E.
hasOfficialLanguageOfLocation
Indicates that a location has a specified language recognized as its official 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_69e0c47c4b9c8190a5586a75f5f36453 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f121da36e88190b42b82641ec54a19 |
completed | April 28, 2026, 9:08 p.m. |
| PD | Predicate disambiguation | batch_69e6be9ebf4c8190892df1a8e1313f88 |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 7:41 p.m.