Triple
T35660858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NEPP |
E1030429
|
entity |
| Predicate | associatedWithVesselHullNumber |
—
|
GENERATED |
| Object | WAGB-20 |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithVesselHullNumber Context triple: [NEPP, associatedWithVesselHullNumber, WAGB-20]
-
A.
associatedWithVoyage
Indicates a relationship where an entity is linked or connected to a specific voyage, journey, or trip.
-
B.
hasVessel
Indicates that one entity possesses, uses, or is associated with a particular vessel (such as a container, ship, or transport medium) in the context of the described relationship or action.
-
C.
hullNumber
chosen
Indicates the unique identifying number assigned to the hull of a ship or vessel.
-
D.
associatedWithHullName
Indicates a relationship where something is linked or connected to a specific hull name, typically identifying the vessel or structure it belongs to.
-
E.
shipAssociatedWith
Indicates that there is a relevant connection or involvement between a ship and another entity, such as ownership, operation, registration, or functional association.
- F. None of above.
Provenance (1 batch)
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_69f76e09f87881909c954aaac176c34f |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:05 p.m.