Triple
T1886729
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Brunswick |
E39980
|
entity |
| Predicate | isOfficiallyBilingual |
P19530
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [New Brunswick, isOfficiallyBilingual, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOfficiallyBilingual Context triple: [New Brunswick, isOfficiallyBilingual, true]
-
A.
isBilingualRegion
Indicates that a region officially uses two languages or has two predominant languages in regular use.
-
B.
additionalOfficialLanguage
Indicates that an entity has another language, beyond its primary one, that holds official or formally recognized status.
-
C.
officialBilingualism
chosen
Indicates that a jurisdiction or institution has formally adopted two languages as having equal official status for government and public functions.
-
D.
oneOfSixOfficialLanguagesOf
Indicates that a language is one of the six officially recognized languages of a particular organization, institution, or entity.
-
E.
isBilingual
Indicates that an entity is able to communicate fluently in two distinct languages.
- 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_69a88633e4fc8190b7eb40463e048ec5 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb12032c881909cd93e3601906f48 |
completed | March 7, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69abafe61bc48190ac9ead027df930e1 |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:34 p.m.