Triple
T28764018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parsnip River |
E726205
|
entity |
| Predicate | hasPoliticalLocation |
P35033
|
FINISHED |
| Object | Canada |
—
|
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: Canada | Statement: [Parsnip River, hasPoliticalLocation, Canada]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPoliticalLocation Context triple: [Parsnip River, hasPoliticalLocation, Canada]
-
A.
politicallyLocatedIn
chosen
Indicates that an entity is situated within or belongs to a particular political or administrative jurisdiction or territory.
-
B.
hasPoliticalPowerBase
Indicates that an entity derives its primary political support, influence, or authority from a particular group, region, or institutional base.
-
C.
hasPoliticalName
Indicates that an entity possesses a specific name or designation used in a political context or for political purposes.
-
D.
isPrimaryPoliticalHubOf
Indicates that a location serves as the main center of political authority, administration, or governance for the referenced entity.
-
E.
hadLocation
Indicates that an entity was situated at, or associated with, a specific location during a particular time or context.
- 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_69f03198be14819098fa74e48b3749bf |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69fd37b695c88190855801626f91c4cd |
completed | May 8, 2026, 1:09 a.m. |
| PD | Predicate disambiguation | batch_69fd374cccf08190a230e87164af5938 |
completed | May 8, 2026, 1:07 a.m. |
Created at: April 28, 2026, 6:12 a.m.