Triple
T5508374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NOAA Ship Ferdinand R. Hassler |
E144500
|
entity |
| Predicate | mmsiNumber |
P65141
|
FINISHED |
| Object | 367191000 |
—
|
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: 367191000 | Statement: [NOAA Ship Ferdinand R. Hassler, mmsiNumber, 367191000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mmsiNumber Context triple: [NOAA Ship Ferdinand R. Hassler, mmsiNumber, 367191000]
-
A.
sailNumber
Indicates the identifying number assigned to a specific sail or sailing vessel, typically used to distinguish it from others.
-
B.
MMSINumber
Indicates a relationship where a mobile subscriber is associated with a specific Mobile Station International ISDN Number (MSISDN) used to identify their phone line in a mobile network.
-
C.
hullNumber
Indicates the unique identifying number assigned to the hull of a ship or vessel.
-
D.
pennantNumber
Indicates the identifying pennant number assigned to a ship or naval vessel.
-
E.
callsign
Indicates that an entity is assigned or uses a specific radio or identification callsign as its designated identifier in communication contexts.
- F. None of above. chosen
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_69c008f6b5048190a09064116062cf69 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01f4a80d88190bab0056c4c78be93 |
completed | March 22, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69c01b07bde08190b3933b96bdc70dd5 |
completed | March 22, 2026, 4:38 p.m. |
| PDg | Predicate description generation | batch_69c01f051e508190b3886d87b4afdd0b |
completed | March 22, 2026, 4:55 p.m. |
Created at: March 22, 2026, 3:33 p.m.