Triple
T2814088
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Capital Region (Canada) |
E54240
|
entity |
| Predicate | hasBilingualStatus |
P21622
|
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: [National Capital Region (Canada), hasBilingualStatus, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBilingualStatus Context triple: [National Capital Region (Canada), hasBilingualStatus, true]
-
A.
isBilingual
Indicates that an entity is able to communicate fluently in two distinct languages.
-
B.
isBilingualRegion
chosen
Indicates that a region officially uses two languages or has two predominant languages in regular use.
-
C.
hasLanguageStatus
Indicates that an entity has a particular status or condition regarding its language use, recognition, or classification.
-
D.
hasSecondaryLanguage
Indicates that an entity possesses or uses a secondary language in addition to its primary language.
-
E.
isBinational
Indicates that an entity is associated with or recognized by two distinct nations, such as holding dual nationality or operating under the authority of two countries.
- 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_69ab49de0af08190b3da69683be1e728 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abde4ba34c819085a336498fc326b0 |
completed | March 7, 2026, 8:14 a.m. |
| PD | Predicate disambiguation | batch_69abdd0740208190911dc9c9546a79ae |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 9:59 p.m.