Triple
T19360341
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | shipwreck of the Peter Iredale |
E484261
|
entity |
| Predicate | vesselRig |
P74366
|
FINISHED |
| Object | four-masted sailing ship |
—
|
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: four-masted sailing ship | Statement: [shipwreck of the Peter Iredale, vesselRig, four-masted sailing ship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vesselRig Context triple: [shipwreck of the Peter Iredale, vesselRig, four-masted sailing ship]
-
A.
vesselFunction
Indicates that one entity serves as the functional role, purpose, or operational use of a vessel in relation to another entity.
-
B.
shipRig
chosen
Indicates that one entity is equipped with or configured using the rigging system specified by another entity.
-
C.
vesselBuilder
Indicates that one entity is the builder, manufacturer, or constructor of a vessel associated with another entity.
-
D.
vesselService
Indicates a service relationship in which one entity provides, operates, or maintains a vessel (such as a ship or boat) for another entity.
-
E.
vesselForm
Indicates that one entity has the physical shape, structure, or configuration of a vessel or container.
- 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_69d8e8d305088190ad13571532aa454c |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e6190c2a8081908f48dfa738248ec8 |
completed | April 20, 2026, 12:16 p.m. |
| PD | Predicate disambiguation | batch_69e4dd13a8cc81909cd02668564c9f29 |
completed | April 19, 2026, 1:48 p.m. |
Created at: April 10, 2026, 1:34 p.m.