Triple
T32479658
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saulnierville |
E830072
|
entity |
| Predicate | officialLanguageInCommunity |
P5562
|
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: [Saulnierville, officialLanguageInCommunity, French]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officialLanguageInCommunity Context triple: [Saulnierville, officialLanguageInCommunity, French]
-
A.
officialLanguage
Indicates that a particular language has been formally designated by an authority as the official language used for government, legal, or administrative purposes in a given jurisdiction.
-
B.
hasLanguageCommunity
chosen
Indicates that an entity is associated with or serves a particular language community.
-
C.
shareOfficialLanguage
Indicates that two entities have at least one official language in common.
-
D.
laterLanguageOfCommunity
Indicates that one language developed later in time as the language used by a particular community, succeeding an earlier community language.
-
E.
declaresOfficialLanguageOf
Indicates that an authority formally designates a particular language as the official language of a specified entity or jurisdiction.
- 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_69f3491ff3b48190b50a7fa00bb05b1f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69ff2636e2bc8190bba91eff91431c6e |
completed | May 9, 2026, 12:19 p.m. |
| PD | Predicate disambiguation | batch_69ff25c65be48190868480d94e1c4e89 |
completed | May 9, 2026, 12:17 p.m. |
Created at: May 1, 2026, 12:58 a.m.