Triple
T3376544
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hyderabad Metro |
E71079
|
entity |
| Predicate | commercialOperationStart |
P3267
|
FINISHED |
| Object | November 2017 |
—
|
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: November 2017 | Statement: [Hyderabad Metro, commercialOperationStart, November 2017]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commercialOperationStart Context triple: [Hyderabad Metro, commercialOperationStart, November 2017]
-
A.
commercialActivity
Indicates an action or relationship involving the buying, selling, or exchange of goods or services for profit or other economic gain.
-
B.
commercialIntroduction
Indicates that one entity introduces or connects another entity to a commercial opportunity, partner, product, or service for business purposes.
-
C.
operationStart
chosen
Indicates the point in time or event at which a specific operation or process begins.
-
D.
commercialStatus
Indicates the current state or condition of something in terms of its commercial availability, activity, or market use.
-
E.
commercialAccess
Indicates that an entity is permitted to use or access something for commercial or profit-generating purposes.
- 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_69ad85a7f80c8190a05e43013f298942 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb2e776508190bc123fb17b36f062 |
completed | March 8, 2026, 5:33 p.m. |
| PD | Predicate disambiguation | batch_69ada433059881908e46f38cc5f40a32 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:13 p.m.