Triple
T6163957
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dhaka Metro Rail |
E137510
|
entity |
| Predicate | systemLengthPlanned |
P22512
|
FINISHED |
| Object | over 100 kilometres |
—
|
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: over 100 kilometres | Statement: [Dhaka Metro Rail, systemLengthPlanned, over 100 kilometres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: systemLengthPlanned Context triple: [Dhaka Metro Rail, systemLengthPlanned, over 100 kilometres]
-
A.
numberPlanned
Indicates that a specific quantity has been scheduled or intended for a future action or allocation.
-
B.
plannedExtensionLength
chosen
Indicates the intended or proposed length of an extension as specified in a plan or design.
-
C.
plannedUnder
Indicates that one entity has been scheduled, organized, or arranged to occur within the scope, authority, or framework of another entity.
-
D.
plannedHeight
Indicates the intended or designed vertical size or elevation that something is planned to have.
-
E.
numberOfRulesPlanned
Indicates the planned or intended count of rules associated with an entity or process.
- 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_69c008a54fc88190b6ce4416490ca79d |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05d6036f88190a4bf540e7fe8d48d |
completed | March 22, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69c055f5b81481908819515cdc334ae6 |
completed | March 22, 2026, 8:49 p.m. |
Created at: March 22, 2026, 4:17 p.m.