Triple
T10143454
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henri Bourassa |
E231642
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Bourassa |
E592592
|
NE 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: Bourassa | Statement: [Henri Bourassa, familyName, Bourassa]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bourassa Context triple: [Henri Bourassa, familyName, Bourassa]
-
A.
Bourassa
chosen
Bourassa is a federal electoral district in Montreal, Quebec, represented in the House of Commons of Canada.
-
B.
Blais
Blais is a variant form of the given name Blaise, used as both a surname and a first name in French-speaking and other cultures.
-
C.
Desmarais
Desmarais is a French surname, often associated with notable families and individuals in business, politics, and the arts.
-
D.
Reaume
Reaume is a surname of likely French origin borne by individuals such as Helen Emma Reaume.
-
E.
Valcartier
Valcartier is a locality in Quebec, Canada, best known for its large Canadian Forces military base and nearby recreational facilities.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ca848364f881908a24366a6feec1db |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cdeb273fec8190818707167e031d58 |
completed | April 2, 2026, 4:05 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d2e618b0bc8190bc1d6f15dac2708e |
completed | April 5, 2026, 10:45 p.m. |
Created at: March 30, 2026, 9:07 p.m.