Triple
T36783483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ironbottom Sound shipwreck sites |
E908836
|
entity |
| Predicate | containsWreckOf |
P49889
|
FINISHED |
| Object | USS Quincy (CA-39) |
—
|
NE NERFINISHED |
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: USS Quincy (CA-39) | Statement: [Ironbottom Sound shipwreck sites, containsWreckOf, USS Quincy (CA-39)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsWreckOf Context triple: [Ironbottom Sound shipwreck sites, containsWreckOf, USS Quincy (CA-39)]
-
A.
containsWreck
Indicates that one entity includes or holds within it the remains or wreckage of another entity.
-
B.
shipwreckInvolved
Indicates that an entity was involved in a shipwreck event, either as a participant, cause, or affected object.
-
C.
wreckSurveyedBy
Indicates that a particular wreck has been examined, measured, or documented by a specified surveying party or method.
-
D.
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.
-
E.
hasShipwrecks
chosen
Indicates that one entity contains, includes, or is associated with shipwrecks located within it or under its control.
- 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_69f76e7a937c81909ed7359641e670f6 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a013f09b0988190ba3179c7d56c726a |
completed | May 11, 2026, 2:29 a.m. |
| PD | Predicate disambiguation | batch_6a013e600e248190a1a9c363702c8586 |
completed | May 11, 2026, 2:26 a.m. |
Created at: May 3, 2026, 4:12 p.m.