Triple
T25825705
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bhopal Metro |
E650523
|
entity |
| Predicate | plannedNumberOfLines |
P4876
|
FINISHED |
| Object | 2 |
—
|
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: 2 | Statement: [Bhopal Metro, plannedNumberOfLines, 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plannedNumberOfLines Context triple: [Bhopal Metro, plannedNumberOfLines, 2]
-
A.
plannedLength
Indicates the intended or scheduled duration or size of something as determined in advance, rather than its actual or realized extent.
-
B.
numberPlanned
Indicates that a specific quantity has been scheduled or intended for a future action or allocation.
-
C.
hasNumberOfLines
chosen
Indicates the relationship that specifies how many lines are associated with a given entity.
-
D.
plannedHeight
Indicates the intended or designed vertical size or elevation that something is planned to have.
-
E.
hasPlannedLine
Indicates that an entity is associated with a specific planned route or line intended for future or scheduled use.
- 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_69e7ab37438081908f1ccf6284839520 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f638d11c988190af7fd4572b08e038 |
completed | May 2, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69f63706b6008190993577193c85ff50 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 22, 2026, 7:36 a.m.