Triple
T23866410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hochelaga |
E592590
|
entity |
| Predicate | hasPoliticalLevel |
P153333
|
FINISHED |
| Object | federal |
—
|
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: federal | Statement: [Hochelaga, hasPoliticalLevel, federal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPoliticalLevel Context triple: [Hochelaga, hasPoliticalLevel, federal]
-
A.
hasElectoralLevel
Indicates that one entity is associated with a specific tier or level within an electoral or voting system.
-
B.
hasPoliticalPower
Indicates that one entity holds authority or influence to make, shape, or enforce political decisions over another entity or within a political system.
-
C.
officeHolderPoliticalLevel
chosen
Indicates the political or administrative level (e.g., local, regional, national) at which an office holder’s position or authority is situated.
-
D.
hasPolity
Indicates that one entity possesses, controls, or is associated with a particular political organization, governance structure, or state-like authority.
-
E.
levelOfPolitics
Indicates the degree or intensity to which something is associated with political content, influence, or activity.
- 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_69e25d22eb488190914b193aff952e83 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1cae47b40819080d1c5294ee59066 |
completed | April 29, 2026, 9:09 a.m. |
| PD | Predicate disambiguation | batch_69f1614a65a88190bde1efb368a151e4 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:13 p.m.