Triple
T36686740
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Warsaw Metro Line M2 stations |
E905836
|
entity |
| Predicate | openedInitialSection |
P20181
|
FINISHED |
| Object | 2015 |
—
|
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: 2015 | Statement: [Warsaw Metro Line M2 stations, openedInitialSection, 2015]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedInitialSection Context triple: [Warsaw Metro Line M2 stations, openedInitialSection, 2015]
-
A.
openedInSection
Indicates that something was opened or initiated within a specific section or subsection of a larger structure or context.
-
B.
openedWithSection
Indicates that something (such as a document, file, or resource) is opened starting from or via a specific section.
-
C.
openedInSections
Indicates that something has been opened or made accessible in multiple distinct sections or parts.
-
D.
firstSectionOpened
chosen
Indicates that the initial section in a sequence or structure has been opened or activated.
-
E.
openedSectionBetween
Indicates that one entity has created or established an open section, gap, or interval between itself and another entity.
- 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_69f76e70d2448190bdd3ce781ba971c5 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd8ccbd4c88190b13aae0673b3c821 |
completed | May 8, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69fd8ae2227c819089546f5c3629799e |
completed | May 8, 2026, 7:04 a.m. |
Created at: May 3, 2026, 4:12 p.m.