Triple
T26223652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tata Steel Jamshedpur Works |
E655829
|
entity |
| Predicate | hasPortLink |
P91695
|
FINISHED |
| Object | connected to ports on the east coast of India |
—
|
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: connected to ports on the east coast of India | Statement: [Tata Steel Jamshedpur Works, hasPortLink, connected to ports on the east coast of India]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPortLink Context triple: [Tata Steel Jamshedpur Works, hasPortLink, connected to ports on the east coast of India]
-
A.
hasPortConnection
Indicates that one entity is linked to another via a port or interface through which data, power, or signals can be transmitted.
-
B.
hasPortOn
Indicates that one entity possesses or is located adjacent to a port situated on another specified geographic or infrastructural feature (such as a coast, river, or lake).
-
C.
hasPorts
Indicates that an entity is equipped with or provides access points (ports) for connection, communication, or interface with other entities or systems.
-
D.
hasPortRole
Indicates that an entity participates in a port with a specified functional or operational role.
-
E.
linkedToPort
chosen
Indicates that one entity is connected or associated with a specific port, such as a network, hardware, or interface port.
- 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_69ee5b4a77e08190bfcb5f8ecdc55abd |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f6bbf6e33c819086e5176d64e7a614 |
completed | May 3, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6b1e6c8190adf9d6a257e0b744 |
completed | May 3, 2026, 3 a.m. |
Created at: April 26, 2026, 8:57 p.m.