Triple
T553678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northwest Passage |
E11895
|
entity |
| Predicate | CanadaClaimsAs |
P16294
|
FINISHED |
| Object | internal waters |
—
|
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: internal waters | Statement: [Northwest Passage, CanadaClaimsAs, internal waters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: CanadaClaimsAs Context triple: [Northwest Passage, CanadaClaimsAs, internal waters]
-
A.
typeOfClaim
Indicates the specific category or nature of a claim being made in relation to an entity or statement.
-
B.
mainClaim
Indicates that one statement is presented as the central or primary assertion being made about a topic.
-
C.
claimsToFollow
Indicates that one entity asserts or professes adherence to the principles, rules, or leadership of another entity.
-
D.
supportsClaim
Indicates that one entity provides evidence, reasoning, or backing that strengthens or validates the truth or credibility of another entity’s claim.
-
E.
hasNotableClaim
Indicates that an entity is associated with a significant, widely recognized statement, assertion, or claim.
- 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_69a4932941d08190815efd422f0b4ca7 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4991b296481908cf27e1d1ec67052 |
completed | March 1, 2026, 7:52 p.m. |
| PD | Predicate disambiguation | batch_69a494bc1f8c8190904356f3a8e801de |
completed | March 1, 2026, 7:34 p.m. |
| PDg | Predicate description generation | batch_69a4985952a481908b918350ececf484 |
completed | March 1, 2026, 7:49 p.m. |
Created at: March 1, 2026, 7:32 p.m.