Triple
T18862252
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parry Island, Ontario |
E461341
|
entity |
| Predicate | hasTypeOfReserve |
P50114
|
FINISHED |
| Object | Indian reserve |
—
|
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: Indian reserve | Statement: [Parry Island, Ontario, hasTypeOfReserve, Indian reserve]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfReserve Context triple: [Parry Island, Ontario, hasTypeOfReserve, Indian reserve]
-
A.
typeOfReserve
chosen
Indicates that one entity is classified as a specific kind or category of reserve in relation to another entity.
-
B.
hasReservationType
Indicates that an entity is associated with a specific category or type of reservation.
-
C.
hasReserveStructure
Indicates that an entity possesses a designated reserve structure, such as an auxiliary or backup organizational or physical framework kept for contingency or support purposes.
-
D.
hasReserveStatus
Indicates that an entity holds a designated reserve or backup status in relation to another entity or role.
-
E.
hasReserveFunction
Indicates that an entity serves as a backup or secondary option that can perform the same function if the primary one is unavailable or fails.
- 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_69d8dcfb7b9c8190854e7b171b98ea2e |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c06184d88190bd05413a07a8c9ce |
completed | April 20, 2026, 5:57 a.m. |
| PD | Predicate disambiguation | batch_69e48d2166b88190add38de96cedc65c |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:57 a.m.