Triple
T20099688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canadiens français |
E496499
|
entity |
| Predicate | notableIdentityMarker |
P22
|
FINISHED |
| Object | use of Quebec 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: use of Quebec French | Statement: [Canadiens français, notableIdentityMarker, use of Quebec French]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableIdentityMarker Context triple: [Canadiens français, notableIdentityMarker, use of Quebec French]
-
A.
hasNotableIdentity
Indicates that an entity is recognized for a specific, distinguished role, status, or identity that makes it notable.
-
B.
notableCityIdentity
Indicates that an entity is recognized or distinguished specifically in the context or identity of a particular city.
-
C.
notableKey
Indicates that the referenced key is of particular importance or prominence compared to other keys in the same context.
-
D.
notableWitness
Indicates that one entity is a significant or prominent witness to an event, action, or situation involving another entity.
-
E.
notableFor
chosen
Indicates that an entity is especially recognized or distinguished for a particular quality, achievement, characteristic, or role.
- 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_69da626eee3881909f3454986d4a6511 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6666f2298819089659f13556ca305 |
completed | April 20, 2026, 5:46 p.m. |
| PD | Predicate disambiguation | batch_69e54cf788188190a46cc49c9ce7617f |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 11:26 p.m.