Triple
T14452444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gujarat Maritime Board |
E358368
|
entity |
| Predicate | typeOfPortsManaged |
P114336
|
FINISHED |
| Object | intermediate ports |
—
|
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: intermediate ports | Statement: [Gujarat Maritime Board, typeOfPortsManaged, intermediate ports]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfPortsManaged Context triple: [Gujarat Maritime Board, typeOfPortsManaged, intermediate ports]
-
A.
typeOfEquipmentManaged
Indicates the specific kind or category of equipment that an entity is responsible for managing.
-
B.
controllerPortCount
Indicates the number of ports available on a given controller.
-
C.
portManagedBy
Indicates that the operation, administration, or control of a port is carried out by a specified managing entity.
-
D.
hasPorts
Indicates that an entity is equipped with or provides access points (ports) for connection, communication, or interface with other entities or systems.
-
E.
hasMaintenancePort
Indicates that an entity is equipped with a dedicated port or interface used specifically for maintenance, diagnostics, or service operations.
- 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_69d82794dfa081909b9134ad2e32244b |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de916244948190bb09d1bfc485ba50 |
completed | April 14, 2026, 7:11 p.m. |
| PD | Predicate disambiguation | batch_69de5c3a02fc819097373f97a260cdeb |
completed | April 14, 2026, 3:24 p.m. |
| PDg | Predicate description generation | batch_69de5fb4de14819092acdecbd201d672 |
completed | April 14, 2026, 3:39 p.m. |
Created at: April 10, 2026, 1:19 a.m.