Triple
T4794797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aboriginal peoples of Canada |
E106684
|
entity |
| Predicate | hasMajorIssue |
P6371
|
FINISHED |
| Object | land claims |
—
|
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: land claims | Statement: [Aboriginal peoples of Canada, hasMajorIssue, land claims]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMajorIssue Context triple: [Aboriginal peoples of Canada, hasMajorIssue, land claims]
-
A.
majorIssue
chosen
Indicates that something is a primary or most significant problem, concern, or obstacle in a given context.
-
B.
hasNotableIssue
Indicates that an entity is associated with a significant problem, concern, or defect that is noteworthy or exceptional compared to typical cases.
-
C.
hasInternalIssue
Indicates that an entity is experiencing a problem, fault, or malfunction originating within itself or its internal components or processes.
-
D.
hasMajorCurrent
Indicates that an entity currently has a primary field of study or specialization.
-
E.
hasMajorPass
Indicates that an entity possesses or is associated with a primary or significant pass (such as a main route, credential, or access authorization).
- 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_69bd43f591c881909e5a532388b0f3f3 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6b40c29c8190adab3503f8ba0145 |
completed | March 20, 2026, 3:44 p.m. |
| PD | Predicate disambiguation | batch_69bd622f88188190a51d52ccfad3d2dd |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:22 p.m.