Triple
T16021349
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS Ark Royal |
E388603
|
entity |
| Predicate | foundWreckLocation |
P6265
|
FINISHED |
| Object | about 30 nautical miles from Gibraltar |
—
|
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: about 30 nautical miles from Gibraltar | Statement: [HMS Ark Royal, foundWreckLocation, about 30 nautical miles from Gibraltar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundWreckLocation Context triple: [HMS Ark Royal, foundWreckLocation, about 30 nautical miles from Gibraltar]
-
A.
wreckLocated
Indicates that the location of a wreck (such as a destroyed vehicle, ship, or structure) is specified or associated with a particular place or area.
-
B.
wreckLocationStatus
Indicates the condition or status of a wreck at a specific location, such as whether it is present, removed, or otherwise changed.
-
C.
wreckDiscovery
chosen
Indicates that an entity discovers, finds, or identifies a wreck (such as a ruined or destroyed object, vehicle, or structure).
-
D.
placeOfSinking
Indicates the location where an object or entity sank or was submerged.
-
E.
containsWreck
Indicates that one entity includes or holds within it the remains or wreckage of another entity.
- 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_69d86dabcb7c8190b6a39d6831d2fa1b |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1858a00888190b8505071575dc56f |
completed | April 17, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e1826a4f7c8190aba6d4f1075141b0 |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 4:55 a.m.