Triple
T37262546
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Batavia shipwreck site |
E924292
|
entity |
| Predicate | operatorOfVessel |
P109038
|
FINISHED |
| Object | Dutch East India Company |
E992
|
NE 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: Dutch East India Company | Statement: [Batavia shipwreck site, operatorOfVessel, Dutch East India Company]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatorOfVessel Context triple: [Batavia shipwreck site, operatorOfVessel, Dutch East India Company]
-
A.
operatesVessel
Indicates that an agent is responsible for controlling, managing, or running the operation of a vessel.
-
B.
usesVesselsOperatedBy
Indicates that one entity makes use of vessels that are operated or controlled by another entity.
-
C.
isVesselFor
Indicates that one entity functions as a container or medium specifically used to hold, carry, or convey another entity.
-
D.
shipOperator
chosen
Indicates the entity that is responsible for operating, managing, or running a ship.
-
E.
vesselService
Indicates a service relationship in which one entity provides, operates, or maintains a vessel (such as a ship or boat) for another entity.
- F. None of above.
Provenance (4 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_69f76eabd6c481909d414a80a1345c98 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a0224f4b6cc8190a8f79700a9af765f |
completed | May 11, 2026, 6:50 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a405124fb90819081595ed217a749b4 |
completed | June 27, 2026, 10:39 p.m. |
| PD | Predicate disambiguation | batch_6a0223f01eb081909419518fdd45f2a4 |
completed | May 11, 2026, 6:46 p.m. |
Created at: May 3, 2026, 4:15 p.m.