Triple
T26173301
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Highway 8 (old numbering) |
E654467
|
entity |
| Predicate | connectedPortCity |
P66192
|
FINISHED |
| Object | 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: Mumbai | Statement: [National Highway 8 (old numbering), connectedPortCity, Mumbai]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectedPortCity Context triple: [National Highway 8 (old numbering), connectedPortCity, Mumbai]
-
A.
hasPortCity
Indicates that a place or region possesses or is associated with a city that functions as its port.
-
B.
connectsCity
Indicates a relationship where one entity serves as a link or route that joins or provides direct access between two cities.
-
C.
linkedCity
Indicates that two entities are associated with each other through a specific city, such as being located in, connected via, or related by that city.
-
D.
connectsCoastalCity
chosen
Indicates a relationship where one entity provides a direct connection or link (such as transport or infrastructure) between coastal cities.
-
E.
connectsInlandCityToCoast
Indicates a relationship where a route, link, or infrastructure connects an inland city to a coastal area or city.
- 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_69ee5b45873c81909499203612d05d07 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f727afd5d88190ad48735cd1b32787 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72737c42c8190a3f781a5e98868ff |
completed | May 3, 2026, 10:45 a.m. |
Created at: April 26, 2026, 8:36 p.m.