Triple
T38330540
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IMO Polar Code |
E1037808
|
entity |
| Predicate | partIBType |
P193980
|
FINISHED |
| Object | recommendatory safety guidance |
—
|
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: recommendatory safety guidance | Statement: [IMO Polar Code, partIBType, recommendatory safety guidance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partIBType Context triple: [IMO Polar Code, partIBType, recommendatory safety guidance]
-
A.
partIAType
Indicates that one entity is classified as a specific type or category of a part within an information architecture.
-
B.
partBType
Indicates that one entity is classified as the type or category to which the second entity (part B) belongs.
-
C.
partCType
Indicates that an entity is classified as a specific subtype or category of a larger part or component.
-
D.
partAType
Indicates that one entity specifies or denotes the type or category of a particular part (part A) in relation to another entity.
-
E.
partDType
Indicates that one entity is classified as a specific subtype or category (type) of a part in relation to another entity.
- 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_69f76e20d65c81909619ac0dd85c56f0 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd5bf69acc819092a01e4259785dc3 |
completed | May 8, 2026, 3:43 a.m. |
| PD | Predicate disambiguation | batch_69fd59b3f4ac8190a7f9dd3142da6e09 |
completed | May 8, 2026, 3:34 a.m. |
| PDg | Predicate description generation | batch_69fd5bf49288819098a12202411cba4f |
completed | May 8, 2026, 3:43 a.m. |
Created at: May 3, 2026, 4:30 p.m.