Triple
T7485830
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Makivik Corporation |
E176878
|
entity |
| Predicate | coManages |
P13336
|
FINISHED |
| Object | Natural resources in Northern Quebec |
—
|
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: Natural resources in Northern Quebec | Statement: [Makivik Corporation, coManages, Natural resources in Northern Quebec]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coManages Context triple: [Makivik Corporation, coManages, Natural resources in Northern Quebec]
-
A.
coManagedWith
chosen
Indicates that two or more entities share joint responsibility or authority in managing the same resource, project, or process.
-
B.
managedIn
Indicates that one entity is administered, operated, or overseen within the scope, control, or jurisdiction of another entity.
-
C.
coAdministersWith
Indicates that one entity is administered together with another entity, typically at the same time or as part of the same treatment or process.
-
D.
hasManagement
Indicates that one entity exercises managerial authority or oversight over another entity.
-
E.
managingCenter
Indicates that one entity serves as the administrative or coordinating center responsible for managing another entity 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_69c69f24ac508190bb98fe927c0bd065 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f556955c8190bf014a065e04c5d8 |
completed | March 27, 2026, 9:23 p.m. |
| PD | Predicate disambiguation | batch_69c6f03eeaa88190a5215772ed05ee9f |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:42 p.m.