Triple
T10606063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MMRDA Metro |
E275878
|
entity |
| Predicate | projectObjective |
P64674
|
FINISHED |
| Object | improve east–west connectivity in 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: improve east–west connectivity in Mumbai | Statement: [MMRDA Metro, projectObjective, improve east–west connectivity in Mumbai]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: projectObjective Context triple: [MMRDA Metro, projectObjective, improve east–west connectivity in Mumbai]
-
A.
subjectOfProject
Indicates that an entity serves as the main focus, topic, or target of a particular project.
-
B.
aimOf
chosen
Indicates that one entity serves as the goal, purpose, or intended target of another entity’s action, plan, or existence.
-
C.
engineeringGoal
Indicates that an entity has a specific engineering-related objective, target, or desired outcome it is intended to achieve or support.
-
D.
fundingObjective
Indicates the purpose or goal for which financial resources are being sought, allocated, or used.
-
E.
projectOutcome
Indicates the resulting state, impact, or consequences produced by carrying out a project.
- 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_69d6aaf948d88190806cc3a8c47a3fb2 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d6df4a5df88190b993196ca7849a88 |
completed | April 8, 2026, 11:05 p.m. |
| PD | Predicate disambiguation | batch_69d6dd72c1288190adbb5e79e94c044a |
completed | April 8, 2026, 10:57 p.m. |
Created at: April 8, 2026, 7:32 p.m.