Triple
T16089563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Muzeum |
E390324
|
entity |
| Predicate | openingDateLineA |
P121858
|
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: [Muzeum, openingDateLineA, 1978-08-12]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openingDateLineA Context triple: [Muzeum, openingDateLineA, 1978-08-12]
-
A.
openingDateLine16
Indicates the date on which line 16 was officially opened or began operation.
-
B.
openingDateLine14
Indicates the date on which something (such as a service, facility, or record) is opened or begins operation, as specified in line 14 of a form or document.
-
C.
openingDate_Line2
Indicates the secondary or alternative date on which something (such as a facility, service, or event) is opened or becomes operational.
-
D.
openingDateLineM1
Indicates the date on which the first line (M1) of a system or service was officially opened or began operation.
-
E.
openingDateOnLine
Indicates the date on which a particular service, facility, or segment first began operating on a specified line.
- 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_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. |
| PDg | Predicate description generation | batch_69e1ff5cd7e481908a29214139a3de2e |
completed | April 17, 2026, 9:37 a.m. |
Created at: April 10, 2026, 4:59 a.m.