Triple
T33540911
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eagle Lake 27 |
E859067
|
entity |
| Predicate | primaryReserveOf |
P144954
|
FINISHED |
| Object | Eagle Lake First Nation |
E244762
|
NE 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: Eagle Lake First Nation | Statement: [Eagle Lake 27, primaryReserveOf, Eagle Lake First Nation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryReserveOf Context triple: [Eagle Lake 27, primaryReserveOf, Eagle Lake First Nation]
-
A.
isOneOfMainReservesOf
Indicates that an entity serves as one of the primary reserve sources or backup resources for another entity.
-
B.
reserves
Indicates that an entity has arranged in advance to hold or secure something for future use or access.
-
C.
isPrimaryReserveOf
chosen
Indicates that one entity serves as the main or principal reserve (backup or stored resource) for another entity.
-
D.
primaryExtraction
Indicates that an entity is the main or initial source from which another entity, resource, or substance is obtained or derived.
-
E.
mainReserve
Indicates that one entity serves as the primary or main reserve resource, backup, or store for another entity.
- F. None of above.
Provenance (4 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_69f3497a5be08190a39b12736899e034 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a475ba1fa548190afbd4e04169f2ef3 |
completed | July 3, 2026, 6:50 a.m. |
| PD | Predicate disambiguation | batch_6a0379f505c88190ac0879ab422c3054 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:39 a.m.