Triple
T19903360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS Resolute |
E478349
|
entity |
| Predicate | returnedAs |
P137762
|
FINISHED |
| Object | gesture of goodwill |
—
|
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: gesture of goodwill | Statement: [HMS Resolute, returnedAs, gesture of goodwill]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: returnedAs Context triple: [HMS Resolute, returnedAs, gesture of goodwill]
-
A.
returnsAs
Indicates that one entity goes back to or resumes a previous state, location, role, or condition associated with another entity.
-
B.
returnedWith
Indicates that an entity came back or was brought back accompanied by, or in possession of, another specified entity.
-
C.
returnedBy
Indicates that something is given, sent, or brought back to a previous sender, owner, or source by another entity.
-
D.
returnedVia
Indicates that something was sent back or responded to through a specified medium, channel, or method.
-
E.
returnedFrom
Indicates that an entity has come back or been sent back from a specified source, location, or prior state.
- 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_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. |
| PDg | Predicate description generation | batch_69e543c136b081909cab9394b958390a |
completed | April 19, 2026, 9:06 p.m. |
Created at: April 10, 2026, 1:52 p.m.