Triple
T9991145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sulpicians |
E196887
|
entity |
| Predicate | roleInMontreal |
P8652
|
FINISHED |
| Object | seigneurs of the Island of Montreal |
—
|
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: seigneurs of the Island of Montreal | Statement: [Sulpicians, roleInMontreal, seigneurs of the Island of Montreal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInMontreal Context triple: [Sulpicians, roleInMontreal, seigneurs of the Island of Montreal]
-
A.
roleInCanada
Indicates that one entity holds or performs a specific role, position, or function within the context of Canada.
-
B.
roleInBordeaux
Indicates that an entity holds or has held a specific role, function, or position within the context of Bordeaux.
-
C.
urbanRole
chosen
Indicates the function, status, or role that an entity holds within an urban or city context.
-
D.
recognizedCommunityInCanada
Indicates that an entity is officially acknowledged or designated as a community within the jurisdiction of Canada.
-
E.
roleInLasVegas
Indicates that an entity holds or held a specific role, position, or function within the context of Las Vegas (such as in its government, organizations, events, or productions).
- 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_69ca82f1678c819093d06320a05f16a4 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdc7a0cb6481908d7bd1b43f93bd18 |
completed | April 2, 2026, 1:34 a.m. |
| PD | Predicate disambiguation | batch_69cd1da07db88190945bcdab3ca82e71 |
completed | April 1, 2026, 1:29 p.m. |
Created at: March 30, 2026, 8:50 p.m.