Triple
T37277028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kabaty–Politechnika |
E924672
|
entity |
| Predicate | openingOrderWithinLine |
P161437
|
FINISHED |
| Object | first southern segment of M1 |
—
|
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: first southern segment of M1 | Statement: [Kabaty–Politechnika, openingOrderWithinLine, first southern segment of M1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openingOrderWithinLine Context triple: [Kabaty–Politechnika, openingOrderWithinLine, first southern segment of M1]
-
A.
openingLineStatus
Indicates the status or condition of an entity’s opening line, such as whether it exists, is valid, or meets a specified criterion.
-
B.
openingDateLineC
Indicates the calendar date on which entity C is opened, initiated, or begins operation.
-
C.
openingLine
Indicates that one entity is the first line or initial statement that begins another entity, such as a text, speech, or conversation.
-
D.
openingDateLineB
Indicates the date on which line B is officially opened or begins operation.
-
E.
openedAsPartOfLine
chosen
Indicates that something (such as a station or segment) was opened concurrently with, and as an integral component of, the launch of a specific line.
- 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_69f76eacdd8c819094080d3991e6d37c |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd57ba740c8190bd1d40166fccccb7 |
completed | May 8, 2026, 3:25 a.m. |
| PD | Predicate disambiguation | batch_69fd55ee82b881908a639da3a41b3af6 |
completed | May 8, 2026, 3:18 a.m. |
Created at: May 3, 2026, 4:16 p.m.