Triple
T5881446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NOAA Ship Okeanos Explorer |
E130757
|
entity |
| Predicate | IMO number |
P65140
|
FINISHED |
| Object | 8835118 |
—
|
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: 8835118 | Statement: [NOAA Ship Okeanos Explorer, IMO number, 8835118]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: IMO number Context triple: [NOAA Ship Okeanos Explorer, IMO number, 8835118]
-
A.
mmsiNumber
Indicates that an entity is associated with a specific Maritime Mobile Service Identity (MMSI) number used for vessel identification.
-
B.
hullNumber
Indicates the unique identifying number assigned to the hull of a ship or vessel.
-
C.
ISONumber
Indicates that an entity is associated with, identified by, or conforms to a specific ISO (International Organization for Standardization) number or standard.
-
D.
sailNumber
Indicates the identifying number assigned to a specific sail or sailing vessel, typically used to distinguish it from others.
-
E.
imoNumber
chosen
Indicates that an entity is associated with a specific International Maritime Organization (IMO) identification number used to uniquely identify ships and certain maritime structures.
- 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_69c0085523688190bfd487479ce819e6 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c03fe07b7081909f8577ec3a9a1a8d |
completed | March 22, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69c0334bdc308190ad0d7199ab975588 |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 3:57 p.m.