Triple
T19903362
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS Resolute |
E478349
|
entity |
| Predicate | returnedDate |
P112129
|
FINISHED |
| Object | 1856 |
—
|
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: 1856 | Statement: [HMS Resolute, returnedDate, 1856]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: returnedDate Context triple: [HMS Resolute, returnedDate, 1856]
-
A.
timeOfReturn
chosen
Indicates the specific time at which an entity comes back to a prior location or state.
-
B.
dateOfReturnAsResidence
Indicates the date on which an entity returned to a particular place to resume or establish it as their residence.
-
C.
deliveryDate
Indicates the specific date on which a product, service, or item is scheduled or expected to be delivered.
-
D.
returnedBy
Indicates that something is given, sent, or brought back to a previous sender, owner, or source by another entity.
-
E.
wasReturnedTo
Indicates that an entity was sent or brought back to a previous owner, location, or state after having been away or removed.
- 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.