Triple
T32387266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | COSCO-HIT Terminals |
E827574
|
entity |
| Predicate | roleInPort |
P130959
|
FINISHED |
| Object | handles significant share of Hong Kong container throughput |
—
|
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: handles significant share of Hong Kong container throughput | Statement: [COSCO-HIT Terminals, roleInPort, handles significant share of Hong Kong container throughput]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInPort Context triple: [COSCO-HIT Terminals, roleInPort, handles significant share of Hong Kong container throughput]
-
A.
hasPortRole
chosen
Indicates that an entity participates in a port with a specified functional or operational role.
-
B.
roleInProtocolStack
Indicates the specific function or position an entity occupies within a layered communication or protocol stack.
-
C.
roleInTheWay
Indicates that one entity is obstructing, hindering, or otherwise blocking another entity’s progress, action, or intended path.
-
D.
roleInName
Indicates that a specific role, title, or position is included as part of an entity’s name or naming expression.
-
E.
roleInGateway
Indicates that an entity holds a specific function or responsibility within a particular gateway system or process.
- 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_69f349184e7481909c6c54428cb9cf12 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a00233e2170819084bee0c8f74cc1a4 |
completed | May 10, 2026, 6:18 a.m. |
| PD | Predicate disambiguation | batch_6a0022943fd08190b73007f080d5971d |
completed | May 10, 2026, 6:15 a.m. |
Created at: May 1, 2026, 12:51 a.m.