Triple
T25776426
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mazagaon |
E649161
|
entity |
| Predicate | hasPortActivityNearby |
P63633
|
FINISHED |
| Object | Mumbai Port Trust |
—
|
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: Mumbai Port Trust | Statement: [Mazagaon, hasPortActivityNearby, Mumbai Port Trust]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPortActivityNearby Context triple: [Mazagaon, hasPortActivityNearby, Mumbai Port Trust]
-
A.
hasNearbyPortAccess
chosen
Indicates that an entity is located close enough to a port to feasibly use it for access or transport.
-
B.
hasNearbyMode
Indicates that one entity has another entity located close enough to be considered in its immediate vicinity or surrounding area.
-
C.
hasOpenSpaceNearby
Indicates that an entity is located near or adjacent to an area that is open, unobstructed, or undeveloped.
-
D.
hasNearbyDiscovery
Indicates that one entity has a discovery located in close physical or spatial proximity to it.
-
E.
hasNearbyAccess
Indicates that one entity has convenient, close-proximity access to another resource, service, or 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_69e7ab333b508190b6d708d8d9a328ed |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f67f0488bc819089fbd2d2478158d3 |
completed | May 2, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69f67e3ed894819094c067c1ef624951 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 22, 2026, 5:34 a.m.