Triple
T36783509
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ironbottom Sound shipwreck sites |
E908836
|
entity |
| Predicate | hasApproximateCountOfWrecks |
P53939
|
FINISHED |
| Object | dozens |
—
|
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: dozens | Statement: [Ironbottom Sound shipwreck sites, hasApproximateCountOfWrecks, dozens]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproximateCountOfWrecks Context triple: [Ironbottom Sound shipwreck sites, hasApproximateCountOfWrecks, dozens]
-
A.
numberOfShipwrecks
chosen
Indicates the quantity of shipwrecks associated with a given entity or context.
-
B.
hasShipwrecks
Indicates that one entity contains, includes, or is associated with shipwrecks located within it or under its control.
-
C.
containsWreck
Indicates that one entity includes or holds within it the remains or wreckage of another entity.
-
D.
wreckDepth
Indicates the depth at which a wreck is located below the water surface.
-
E.
shipwrecksRecoveredIn
Indicates the location or context in which shipwrecks have been found and recovered.
- 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_69fe629b4fa481908467c7c41b77f0c6 |
completed | May 8, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69fe61bb260c819083f9378a3a06ca47 |
completed | May 8, 2026, 10:20 p.m. |
Created at: May 3, 2026, 4:12 p.m.