Triple
T26139556
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Little Canyon (Stikine) |
E659477
|
entity |
| Predicate | name |
P16
|
FINISHED |
| Object |
Little Canyon
Little Canyon is a narrow, steep-walled gorge along the Stikine River in northwestern British Columbia, Canada, known for its rugged scenery and powerful river flow.
|
E1765554
|
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: Little Canyon | Statement: [Little Canyon (Stikine), name, Little Canyon]
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Little Canyon Triple: [Little Canyon (Stikine), name, Little Canyon]
Generated description
Little Canyon is a narrow, steep-walled gorge along the Stikine River in northwestern British Columbia, Canada, known for its rugged scenery and powerful river flow.
Provenance (5 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_69ee5bc3c20c8190bf2cf272f4170e95 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f60be30d14819088ccd8f162874346 |
completed | May 2, 2026, 2:36 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a129c791bc88190ad59b6f207d37633 |
completed | May 24, 2026, 6:36 a.m. |
| NEDg | Description generation | batch_6a129cdeb5a48190a9d63b019074e2de |
completed | May 24, 2026, 6:38 a.m. |
| NED2 | Entity disambiguation (via description) | batch_6a129d64f3dc81909fe9ccc1db2ddaa1 |
completed | May 24, 2026, 6:40 a.m. |
Created at: April 26, 2026, 8:19 p.m.