Triple
T38012786
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UN 1671 |
E948409
|
entity |
| Predicate | hasProperShippingName |
P207554
|
FINISHED |
| Object | Phenol |
—
|
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: Phenol | Statement: [UN 1671, hasProperShippingName, Phenol]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProperShippingName Context triple: [UN 1671, hasProperShippingName, Phenol]
-
A.
hasShipName
Indicates that an entity (such as a vessel or record) is associated with a specific ship name.
-
B.
hasShipPrefix
Indicates that a ship is associated with or identified by a specific prefix in its name or designation.
-
C.
containsShippingRoute
Indicates that one location or area includes within its boundaries a shipping route used for transporting goods or vessels.
-
D.
hasProperName
Indicates that an entity is associated with a specific proper name used to uniquely identify it.
-
E.
hasShippingLaneType
Indicates the specific category or type of shipping lane associated with a given route or area.
- 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_69f76efb4b10819092c8c2ba28ac06a8 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037df1223c8190a5d61e4f8e6fd613 |
completed | May 12, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_6a037a1ad6c48190bfe35d350c1b4751 |
completed | May 12, 2026, 7:06 p.m. |
| PDg | Predicate description generation | batch_6a037df009f4819082e04683e6e8a106 |
completed | May 12, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:20 p.m.