Triple
T16089601
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Můstek |
E390325
|
entity |
| Predicate | openingDateLineASection |
P93179
|
FINISHED |
| Object | 1978-08-12 |
—
|
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: 1978-08-12 | Statement: [Můstek, openingDateLineASection, 1978-08-12]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openingDateLineASection Context triple: [Můstek, openingDateLineASection, 1978-08-12]
-
A.
lineSectionOpeningDate
chosen
Indicates the date on which a specific section of a line (e.g., a route, track, or corridor) was officially opened for use.
-
B.
openedSectionBetween
Indicates that one entity has created or established an open section, gap, or interval between itself and another entity.
-
C.
openedWithSection
Indicates that something (such as a document, file, or resource) is opened starting from or via a specific section.
-
D.
openedInSection
Indicates that something was opened or initiated within a specific section or subsection of a larger structure or context.
-
E.
isOpeningSectionOf
Indicates that one content segment functions as the initial or introductory section of another, larger work or structure.
- 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_69d87f198bc48190a8b7e53ca15b7ead |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e1ff63edb0819092cbb671967bbdcd |
completed | April 17, 2026, 9:37 a.m. |
| PD | Predicate disambiguation | batch_69e1827ad7c88190b867da511cbfb7fa |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 4:59 a.m.