Triple
T9174245
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS Levant |
E220155
|
entity |
| Predicate | recaptureLocation |
P26805
|
FINISHED |
| Object | off Madeira |
—
|
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: off Madeira | Statement: [HMS Levant, recaptureLocation, off Madeira]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recaptureLocation Context triple: [HMS Levant, recaptureLocation, off Madeira]
-
A.
recountLocation
Indicates that an entity narrates or describes events or experiences associated with a particular location.
-
B.
rescuedLocation
chosen
Indicates the place where a rescue action occurred or from which someone or something was rescued.
-
C.
recaptureDate
Indicates the date on which something that was previously captured or held is captured or taken back again.
-
D.
recaptureContext
Indicates that a previously established context or situation is being regained or restored after it was lost, interrupted, or diminished.
-
E.
reserveLocation
Indicates that an entity designates or sets aside a specific place for a particular use, purpose, or future activity.
- 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_69ca83e467108190abcae6a33b3d4dad |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccbfa128d48190b54b8f95d77d81cc |
completed | April 1, 2026, 6:48 a.m. |
| PD | Predicate disambiguation | batch_69cc660761d88190ab6134b43b376964 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:23 p.m.