Triple
T8711480
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1908–1909 North Pole expedition |
E206786
|
entity |
| Predicate | statusOfClaim |
P84014
|
FINISHED |
| Object | disputed |
—
|
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: disputed | Statement: [1908–1909 North Pole expedition, statusOfClaim, disputed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusOfClaim Context triple: [1908–1909 North Pole expedition, statusOfClaim, disputed]
-
A.
complainantStatus
Indicates the role or standing of the person or party making a complaint in relation to the case or issue.
-
B.
claimProcess
Indicates the process by which a claim (such as an insurance or service claim) is received, evaluated, and resolved between involved parties.
-
C.
appealStatus
Indicates the current state or outcome of an appeal within a review or decision process.
-
D.
statusIndicates
Indicates that a particular status value conveys or reflects the current condition, state, or situation of an entity or process.
-
E.
allegedStatus
Indicates that a particular status or condition is claimed or asserted about an entity, but has not been confirmed as true.
- 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_69ca83572d4881909bef3be2b578d539 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5c3189f88190bb9bb77ba9d28d60 |
completed | March 31, 2026, 11:43 p.m. |
| PD | Predicate disambiguation | batch_69cc456e806c819087e7d66ee737f242 |
completed | March 31, 2026, 10:06 p.m. |
| PDg | Predicate description generation | batch_69cc46c330bc8190a9b644078881c6ff |
completed | March 31, 2026, 10:12 p.m. |
Created at: March 30, 2026, 6:35 p.m.