Triple
T19903350
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS Resolute |
E478349
|
entity |
| Predicate | abandonedDate |
P49984
|
FINISHED |
| Object | 1854 |
—
|
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: 1854 | Statement: [HMS Resolute, abandonedDate, 1854]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: abandonedDate Context triple: [HMS Resolute, abandonedDate, 1854]
-
A.
dateOfAbandonment
chosen
Indicates the specific date on which something (such as a place, project, or object) was formally or effectively abandoned or discontinued.
-
B.
abandonedReason
Indicates the reason or cause for which something was abandoned, discontinued, or given up.
-
C.
abandonedBefore
Indicates that one entity ceased or gave up on something prior in time to another entity doing so.
-
D.
abandonedIn
Indicates that one entity was left behind or deserted in the location or context specified by another entity.
-
E.
abandonedBy
Indicates that one entity has been deserted, forsaken, or left behind by another entity that was previously present, responsible, or involved.
- 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_69d8e520682081909892916424699bd5 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65944c55481909b54a8f9a9c087d6 |
completed | April 20, 2026, 4:50 p.m. |
| PD | Predicate disambiguation | batch_69e537ecda248190895c96afb6243823 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:52 p.m.