Triple
T15065476
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rapid Metro (defunct) |
E379743
|
entity |
| Predicate | servedPurpose |
P79
|
FINISHED |
| Object | improving connectivity between Gurugram and Delhi |
—
|
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: improving connectivity between Gurugram and Delhi | Statement: [Rapid Metro (defunct), servedPurpose, improving connectivity between Gurugram and Delhi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedPurpose Context triple: [Rapid Metro (defunct), servedPurpose, improving connectivity between Gurugram and Delhi]
-
A.
servicePurpose
Indicates that one entity serves as the purpose, goal, or intended function for which another entity (typically a service) exists or is provided.
-
B.
purpose
chosen
Indicates that one entity exists, is done, or is used in order to achieve, support, or serve the goal, function, or intended outcome of another entity.
-
C.
intendedToServe
Indicates that one entity was designed, planned, or purposed specifically to benefit, assist, or fulfill the needs of another entity.
-
D.
operationalPurpose
Indicates the function, role, or intended use that an entity is designed or configured to perform in an operational context.
-
E.
meetsForPurpose
Indicates that one entity meets with another specifically to pursue or accomplish a particular purpose or objective.
- 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_69d85cd7683881908d405c1b5d7b4f7f |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69dedeea750c819082d8823c9ab6c5a2 |
completed | April 15, 2026, 12:42 a.m. |
| PD | Predicate disambiguation | batch_69deb95a182081908fffc4402b02a394 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:02 a.m.