Triple
T21365838
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nhava Island |
E526909
|
entity |
| Predicate | portTypeHosted |
P143999
|
FINISHED |
| Object | container port |
—
|
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 port | Statement: [Nhava Island, portTypeHosted, container port]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: portTypeHosted Context triple: [Nhava Island, portTypeHosted, container port]
-
A.
guestHosted
Indicates that one entity temporarily hosted or presented an event, show, or program in place of or alongside the usual host.
-
B.
hostedOn
Indicates that one entity operates, resides, or is made available on another entity that provides the underlying platform or infrastructure.
-
C.
portSystem
Indicates that one system serves as a port or interface through which another system connects, communicates, or transfers data or resources.
-
D.
hosted
Indicates that one entity organized and provided the venue or platform for an event, activity, or presence involving another entity.
-
E.
registeredPort
Indicates that a specific network port number has been officially assigned and recorded for use by a particular service or protocol.
- 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_69e0b51d8a308190b09113b3b3f9bc15 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e8b06ec4208190b9ed3484afd85852 |
completed | April 22, 2026, 11:26 a.m. |
| PD | Predicate disambiguation | batch_69e6162bbfc88190a3e75859941b2638 |
completed | April 20, 2026, 12:03 p.m. |
| PDg | Predicate description generation | batch_69e61b3e47f881908fb2aac9bd2bfb58 |
completed | April 20, 2026, 12:25 p.m. |
Created at: April 16, 2026, 5:09 p.m.