Triple
T783160
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Musashi |
E16541
|
entity |
| Predicate | wreckDiscoveredBy |
P6265
|
FINISHED |
| Object | expedition funded by Paul Allen |
—
|
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: expedition funded by Paul Allen | Statement: [Musashi, wreckDiscoveredBy, expedition funded by Paul Allen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wreckDiscoveredBy Context triple: [Musashi, wreckDiscoveredBy, expedition funded by Paul Allen]
-
A.
wreckDiscovery
chosen
Indicates that an entity discovers, finds, or identifies a wreck (such as a ruined or destroyed object, vehicle, or structure).
-
B.
placeOfSinking
Indicates the location where an object or entity sank or was submerged.
-
C.
sunkBy
Indicates that one entity (typically a vessel or structure) was caused to sink or be destroyed in water by another entity.
-
D.
shipwreckedOn
Indicates that an entity becomes stranded or marooned on a particular landmass or location as a result of a shipwreck.
-
E.
hasTypeOfWreck
Indicates that one entity is classified as a specific type or category of wreck (e.g., shipwreck, car wreck) associated with 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_69a4936ad1fc81908f190208059ccf78 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a7686d0881908c2a4395059be02c |
completed | March 1, 2026, 8:54 p.m. |
| PD | Predicate disambiguation | batch_69a4a50db97c8190a1c55673f4a357b4 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.