Triple
T28103589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tête-de-Boule |
E710301
|
entity |
| Predicate | provinceContext |
P604
|
FINISHED |
| Object | Quebec |
—
|
NE NERFINISHED |
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: Quebec | Statement: [Tête-de-Boule, provinceContext, Quebec]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: provinceContext Context triple: [Tête-de-Boule, provinceContext, Quebec]
-
A.
province
chosen
Indicates that one entity is an administrative subdivision or region (a province) governed by or belonging to another, typically larger, political or territorial entity.
-
B.
districtContext
Indicates that something occurs within, is associated with, or is interpreted in the context of a particular district or administrative area.
-
C.
regionContext
Indicates the broader geographic or spatial setting within which an entity, event, or relationship is situated or interpreted.
-
D.
provinceMetropolitanSee
Indicates that a metropolitan see (an archdiocesan seat) has ecclesiastical jurisdiction over, or is the principal see of, a given church province.
-
E.
provinceSupplied
Indicates that a province is provided, furnished, or supplied by a specified source or entity.
- 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_69ef9b71fdb081908b4a61cd7ff147c1 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f78c61ed4c8190ad84c918fa9af55a |
completed | May 3, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69f78b8cb3a881909ebaac1b503988c2 |
completed | May 3, 2026, 5:53 p.m. |
Created at: April 27, 2026, 9:06 p.m.