Triple
T29709182
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jewar |
E751727
|
entity |
| Predicate | proposedMetroConnectivityTo |
P60933
|
FINISHED |
| Object | Noida |
—
|
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: Noida | Statement: [Jewar, proposedMetroConnectivityTo, Noida]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: proposedMetroConnectivityTo Context triple: [Jewar, proposedMetroConnectivityTo, Noida]
-
A.
connectsMetroAreas
Indicates a relationship where a transportation route or service links two or more metropolitan areas, enabling direct travel or interaction between them.
-
B.
hasMetropolitanConnectionWith
Indicates that there is a significant relationship or linkage between two entities based on shared or interacting metropolitan areas, such as through infrastructure, services, or regional integration.
-
C.
connectsCityTo
chosen
Indicates a relationship in which a route, infrastructure, or link joins one city to another, enabling connection or interaction between them.
-
D.
hasLightRailStationPlanned
Indicates that a light rail station is planned or scheduled to be built at or associated with the given entity.
-
E.
hasPublicTransportConnection
Indicates that there is an available public transportation link or service connecting the related entities.
- 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_69f0d62748848190b030d0a703629a7d |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f7117e55908190a67105e92bc4830f |
completed | May 3, 2026, 9:12 a.m. |
| PD | Predicate disambiguation | batch_69f70f380690819090cc34763ba460ed |
completed | May 3, 2026, 9:02 a.m. |
Created at: April 28, 2026, 7:29 p.m.