Triple
T2486678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mumbai Monorail |
E55941
|
entity |
| Predicate | designedToConnect |
P9494
|
FINISHED |
| Object | eastern suburbs of Mumbai |
—
|
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: eastern suburbs of Mumbai | Statement: [Mumbai Monorail, designedToConnect, eastern suburbs of Mumbai]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedToConnect Context triple: [Mumbai Monorail, designedToConnect, eastern suburbs of Mumbai]
-
A.
connectsTo
Indicates a relationship where one entity is linked or joined to another, allowing interaction, communication, or transfer between them.
-
B.
connectorType
Indicates the specific kind or category of connection interface that links two entities.
-
C.
isTypicallyWiredUsing
Indicates that one thing is commonly connected or implemented using a particular type of wiring or cabling.
-
D.
connectsUnder
Indicates that one entity forms a connection to another entity by passing beneath or under it.
-
E.
isDesignedFor
chosen
Indicates that one entity has been created, planned, or optimized specifically to serve the needs, purposes, or use of another entity.
- 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_69ab49e670a88190b928e08302381710 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd20b6d008190acec0eb172e218c9 |
completed | March 7, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69abd0b7cf088190bcff4dac6150044c |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:45 p.m.