Triple
T2259199
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ever Given |
E49997
|
entity |
| Predicate | MMSINumber |
P36794
|
FINISHED |
| Object | 353136000 |
—
|
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: 353136000 | Statement: [Ever Given, MMSINumber, 353136000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: MMSINumber Context triple: [Ever Given, MMSINumber, 353136000]
-
A.
SSNumber
Indicates that an entity has a specific Social Security Number assigned to it.
-
B.
serviceNumber
Indicates a unique identifying number assigned to a service, used to reference, track, or distinguish that service from others.
-
C.
associatedNumber
Indicates a relationship where a specific number is linked or assigned to an entity as its associated value.
-
D.
hasTelephoneService
Indicates that a subject is provided with or connected to telephone service.
-
E.
administrativeNumber
Indicates that an entity is associated with a specific official identification or reference number used for administrative purposes.
- 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_69a88b01e0048190ba96431b5f990ba9 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abc15ad06c8190b6d0babc17015787 |
completed | March 7, 2026, 6:10 a.m. |
| PD | Predicate disambiguation | batch_69abbdb34c148190b51e99f540f97204 |
completed | March 7, 2026, 5:54 a.m. |
| PDg | Predicate description generation | batch_69abbe86dbcc81908c72793af8fe2a4d |
completed | March 7, 2026, 5:58 a.m. |
Created at: March 4, 2026, 7:48 p.m.