Triple
T17206970
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gitwangak |
E417627
|
entity |
| Predicate | Gitwangak Battle Hill |
P126405
|
FINISHED |
| Object | National Historic Site of Canada |
—
|
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: National Historic Site of Canada | Statement: [Gitwangak, Gitwangak Battle Hill, National Historic Site of Canada]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Gitwangak Battle Hill Context triple: [Gitwangak, Gitwangak Battle Hill, National Historic Site of Canada]
-
A.
notableStructureOnHill
Indicates that a notable or significant structure is located on top of, or situated upon, a hill.
-
B.
mainHillName
Indicates that the subject’s primary or most prominent hill is identified by the given name.
-
C.
Pico Bill
Indicates a legislative proposal or law specifically related to pico-scale or very small-scale matters, actions, or regulations.
-
D.
hillTemple
Indicates a relationship where a temple is located on, associated with, or dedicated to a hill.
-
E.
isHighlandLandmarkFor
Indicates that a landmark is recognized as a notable or defining feature specifically within a highland area or region.
- F. None of above. chosen
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_69d886d6ba8c819093215917b3d01689 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42dc193488190a2c5a48ce7f631a9 |
completed | April 19, 2026, 1:20 a.m. |
| PD | Predicate disambiguation | batch_69e3831e354881908c5505ffd15c84e9 |
completed | April 18, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69e3873f62108190966c4e741ebd548d |
completed | April 18, 2026, 1:29 p.m. |
Created at: April 10, 2026, 5:38 a.m.