Triple
T33812862
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Warszawa Wschodnia railway station |
E866585
|
entity |
| Predicate | namedAfterDirection |
P189471
|
FINISHED |
| Object | eastern part of Warsaw |
—
|
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: eastern part of Warsaw | Statement: [Warszawa Wschodnia railway station, namedAfterDirection, eastern part of Warsaw]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namedAfterDirection Context triple: [Warszawa Wschodnia railway station, namedAfterDirection, eastern part of Warsaw]
-
A.
namedAfter
Indicates that one entity has been given its name in honor of, or derived from, another entity.
-
B.
namedAfterPosition
Indicates that an entity is named after a specific position, role, or rank associated with it.
-
C.
namedAfterSuccessor
Indicates that an entity is named after another entity that succeeds or follows it in time, position, or sequence.
-
D.
containsDirectionOf
Indicates that one entity includes or encompasses the directional orientation or path associated with another entity.
-
E.
namedAfterSince
Indicates that one entity has borne the name of another entity starting from a specific point in time.
- F. None of above. chosen
Provenance (4 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_69f349911a8c81908478662194b23d8c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd13595c81908719f52c3d37a7e8 |
completed | May 6, 2026, 10:13 p.m. |
| PDg | Predicate description generation | batch_69fbc36bcac48190a726b40442c094d1 |
completed | May 6, 2026, 10:40 p.m. |
Created at: May 1, 2026, 1:46 a.m.