Triple
T23577935
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sohar |
E580314
|
entity |
| Predicate | hasPortActivityType |
P20949
|
FINISHED |
| Object | container shipping |
—
|
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: container shipping | Statement: [Sohar, hasPortActivityType, container shipping]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPortActivityType Context triple: [Sohar, hasPortActivityType, container shipping]
-
A.
hasActivityType
chosen
Indicates the specific kind or category of activity associated with an entity or event.
-
B.
hasPortTraffic
Indicates that there is a flow or volume of traffic (such as ships, cargo, or passengers) associated with a particular port.
-
C.
portActivity
Indicates the level or type of operational activity occurring at a port, such as ship movements, cargo handling, or related maritime operations.
-
D.
hasPortType
Indicates that an entity is associated with, or characterized by, a specific type or category of port.
-
E.
hasPortRole
Indicates that an entity participates in a port with a specified functional or operational role.
- 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_69e24601a9108190bc31e83833c980e4 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1afd725d88190b33c8fb26603db59 |
completed | April 29, 2026, 7:14 a.m. |
| PD | Predicate disambiguation | batch_69f118bcc0b08190b25a8dddfd461a0e |
completed | April 28, 2026, 8:29 p.m. |
Created at: April 17, 2026, 6:38 p.m.