Triple
T25997985
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M28 line |
E646538
|
entity |
| Predicate | isPlannedToImprove |
P4375
|
FINISHED |
| Object | public transport capacity in Istanbul |
—
|
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: public transport capacity in Istanbul | Statement: [M28 line, isPlannedToImprove, public transport capacity in Istanbul]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPlannedToImprove Context triple: [M28 line, isPlannedToImprove, public transport capacity in Istanbul]
-
A.
seeksToImprove
Indicates an intentional effort by one entity to make another entity or condition better than its current state.
-
B.
hasImproved
Indicates that an entity’s state, quality, or performance has become better compared to a previous point in time.
-
C.
claimsToImprove
Indicates that one entity asserts or promises that it will enhance, benefit, or make another entity better in some way.
-
D.
hasImprovementProgram
Indicates that an entity is associated with, participates in, or is covered by a program specifically designed to improve its performance, condition, or quality.
-
E.
plannedUpgrade
chosen
Indicates that an entity has a scheduled or intended improvement or enhancement to be carried out in the future.
- 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_69e77e88cb8481908da31d4a00661f55 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6057012248190a486e723fdd2107e |
completed | May 2, 2026, 2:08 p.m. |
| PD | Predicate disambiguation | batch_69f5aff889988190ad10bcf1a280f717 |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 22, 2026, 8:58 a.m.