Triple
T37114813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jawaharlal Nehru Port Authority |
E919088
|
entity |
| Predicate | portManagedLocatedIn |
P35739
|
FINISHED |
| Object | Navi Mumbai |
—
|
NE NERFINISHED |
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: Navi Mumbai | Statement: [Jawaharlal Nehru Port Authority, portManagedLocatedIn, Navi Mumbai]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: portManagedLocatedIn Context triple: [Jawaharlal Nehru Port Authority, portManagedLocatedIn, Navi Mumbai]
-
A.
portManagedBy
Indicates that the operation, administration, or control of a port is carried out by a specified managing entity.
-
B.
portLocation
chosen
Indicates that a port is geographically situated at or associated with a specific location.
-
C.
boundaryManagedBy
Indicates that the defined boundary is overseen, controlled, or administered by a specific managing entity.
-
D.
locatedIn
Indicates that one entity exists or is situated within the spatial, administrative, or conceptual boundaries of another entity.
-
E.
portalLocation
Indicates that a portal is situated at or associated with a specific location.
- 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_69f76e9c57148190ba789dd059645bb9 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb55de3b9c8190a7656aeab3c3ffbc |
completed | May 6, 2026, 2:53 p.m. |
| PD | Predicate disambiguation | batch_69fb35bc92e08190bff447624e2df791 |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 3, 2026, 4:15 p.m.