Triple
T24280559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hyundai Mipo Dockyard |
E605526
|
entity |
| Predicate | hasMajorClientType |
P79955
|
FINISHED |
| Object | global shipping companies |
—
|
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: global shipping companies | Statement: [Hyundai Mipo Dockyard, hasMajorClientType, global shipping companies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMajorClientType Context triple: [Hyundai Mipo Dockyard, hasMajorClientType, global shipping companies]
-
A.
hasNotableClientType
chosen
Indicates that an entity has clients belonging to a particular notable or distinguished category or type.
-
B.
hasMajorType
Indicates that an entity belongs to or is categorized under a primary or overarching type or classification.
-
C.
hasMajorTenantType
Indicates that an entity (such as a property or building) is associated with a primary or predominant type of tenant.
-
D.
hasClient
Indicates that an entity maintains a client relationship with another entity, typically as a provider of goods or services.
-
E.
hasMajorCategory
Indicates that something is associated with or classified under a primary, overarching category.
- 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_69e295480d0c8190846fc3c2e2da1d4c |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28f5227888190b1713af150fa30a1 |
completed | April 29, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69f1c457a2908190993824395b3c365d |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:07 a.m.