Triple
T8442292
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oregon Treaty of 1846 |
E199577
|
entity |
| Predicate | containsClauseOn |
P12721
|
FINISHED |
| Object | navigation of the Columbia River |
—
|
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: navigation of the Columbia River | Statement: [Oregon Treaty of 1846, containsClauseOn, navigation of the Columbia River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsClauseOn Context triple: [Oregon Treaty of 1846, containsClauseOn, navigation of the Columbia River]
-
A.
includesClause
chosen
Indicates that one entity (typically a document, contract, or statement) contains or incorporates a specific clause as part of its content.
-
B.
hasClauseStructure
Indicates that one linguistic unit exhibits a particular internal clause configuration or pattern in relation to another specified clause structure.
-
C.
containsPolicyOn
Indicates that one entity includes, references, or incorporates a specific policy within it.
-
D.
hasConjunction
Indicates that two or more entities are linked together by a coordinating conjunction, forming a combined or joint relationship.
-
E.
hasClaimOn
Indicates that one entity holds a right, entitlement, or demand over another entity or its resources.
- 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_69ca83170f9081909cd98f55614c6476 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe30fba4081908bfdef3faf5baceb |
completed | March 31, 2026, 3:06 p.m. |
| PD | Predicate disambiguation | batch_69cbd0f5a3648190beb53a139a2d5482 |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:08 p.m.