Triple
T10624600
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | H3RC |
E250289
|
entity |
| Predicate | associatedWithIMOShipNumber |
P62262
|
FINISHED |
| Object | IMO 9811000 |
—
|
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: IMO 9811000 | Statement: [H3RC, associatedWithIMOShipNumber, IMO 9811000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithIMOShipNumber Context triple: [H3RC, associatedWithIMOShipNumber, IMO 9811000]
-
A.
shipAssociatedWith
chosen
Indicates that there is a relevant connection or involvement between a ship and another entity, such as ownership, operation, registration, or functional association.
-
B.
shipsWith
Indicates that one entity is delivered, packaged, or provided together with another entity as part of the same shipment or bundle.
-
C.
associatedWithSea
Indicates a relationship in which something has a connection, relevance, or linkage to the sea or marine environment.
-
D.
associatedWithSeaRoute
Indicates a relationship where something is connected or related to a particular sea route, such as by use, location, or relevance.
-
E.
shipInvolved
Indicates that a ship participates in, is associated with, or plays a role in a specified event or situation.
- 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_69d6aa5993448190a493b790b8f85010 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6df7fe9fc81908b3b8d1dc06a829c |
completed | April 8, 2026, 11:06 p.m. |
| PD | Predicate disambiguation | batch_69d6dd7fae088190973f70c69738af49 |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 8:53 p.m.