Triple
T20206088
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dawson Creek, British Columbia |
E493354
|
entity |
| Predicate | incorporationAs |
P13056
|
FINISHED |
| Object | village |
—
|
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: village | Statement: [Dawson Creek, British Columbia, incorporationAs, village]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: incorporationAs Context triple: [Dawson Creek, British Columbia, incorporationAs, village]
-
A.
incorporatedAs
chosen
Indicates that an organization has been legally formed and registered under a specific corporate structure or name.
-
B.
incorporationAfter
Indicates that one entity is incorporated or formally established at a later time than another entity.
-
C.
incorporationDescription
Indicates that a description is provided explaining the details, terms, or nature of an incorporation event or process.
-
D.
incorporatedThrough
Indicates that one entity was formed, established, or legally created by means of another specified process, mechanism, or intermediary entity.
-
E.
incorporationPolicy
Indicates the rules or conditions under which one entity is formally integrated or merged into another entity or system.
- 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_69da6269614c8190bb40475d9d477358 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66d922ebc8190ae012da8ceba74dd |
completed | April 20, 2026, 6:16 p.m. |
| PD | Predicate disambiguation | batch_69e55b14c9d8819095453d0504d9222f |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:38 p.m.