Triple
T17750254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kotelnica Białczańska |
E443092
|
entity |
| Predicate | hasApproximateOpeningMonths |
P100126
|
FINISHED |
| Object | December |
—
|
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: December | Statement: [Kotelnica Białczańska, hasApproximateOpeningMonths, December]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproximateOpeningMonths Context triple: [Kotelnica Białczańska, hasApproximateOpeningMonths, December]
-
A.
openingDateApproximate
Indicates that the date when something was opened or began is not known exactly and is only an approximate value.
-
B.
operatingMonthsApproximate
chosen
Indicates that the time period during which something operates is specified in approximate months rather than exact dates.
-
C.
typicallyOpenFromMonth
Indicates the month from which something (such as a place, service, or facility) is usually open or begins operating.
-
D.
plannedOpeningDate
Indicates the date on which something is scheduled or intended to begin operating or become available.
-
E.
expansionOpeningDate
Indicates the date on which an expansion of something (such as a facility, service, or project) was officially opened or became operational.
- 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_69d8b9ed3a2081909b2ec0d4dd2f4c37 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4841a401c8190ae1dc0ed7ae4cc26 |
completed | April 19, 2026, 7:28 a.m. |
| PD | Predicate disambiguation | batch_69e3cde9dc288190af0e2198487f2051 |
completed | April 18, 2026, 6:31 p.m. |
Created at: April 10, 2026, 10:10 a.m.