Triple
T4534535
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Delhi Metro Rail Corporation |
E106374
|
entity |
| Predicate | operatesSystemType |
P3941
|
FINISHED |
| Object | metro rail system |
—
|
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: metro rail system | Statement: [Delhi Metro Rail Corporation, operatesSystemType, metro rail system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatesSystemType Context triple: [Delhi Metro Rail Corporation, operatesSystemType, metro rail system]
-
A.
operatesSystem
chosen
Indicates that an entity actively controls, manages, or runs a particular system.
-
B.
operatingSystem
Indicates that one entity is the operating system running on, or used by, another entity.
-
C.
operatorSystem
Indicates a relationship where one entity functions as the operating system that manages or controls another entity (such as a device, application, or system).
-
D.
systemType
Indicates the classification or category of a system that an entity belongs to or operates as.
-
E.
primaryOperatingEnvironment
Indicates the main environment, platform, or context in which an entity is primarily designed to operate or function.
- 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_69bd43f3d6e08190a91824f833d51bbe |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd57a2301c8190aa59280a16750156 |
completed | March 20, 2026, 2:20 p.m. |
| PD | Predicate disambiguation | batch_69bd521edd00819099dfccaa65dddd61 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:04 p.m.