Triple
T9401830
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elbing |
E226489
|
entity |
| Predicate | presentDayNameUsedSince |
P88742
|
FINISHED |
| Object | after 1945 |
—
|
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: after 1945 | Statement: [Elbing, presentDayNameUsedSince, after 1945]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: presentDayNameUsedSince Context triple: [Elbing, presentDayNameUsedSince, after 1945]
-
A.
knownTodayAs
Indicates that an entity is currently referred to or recognized by a particular name or designation in the present time.
-
B.
dayName
Indicates the specific name of the day of the week associated with a given date or time.
-
C.
presentDayNameOfCapital
Indicates that one entity is the current, officially used name of the capital city associated with another entity.
-
D.
mentionsDayOfWeek
Indicates that something explicitly refers to or names a specific day of the week.
-
E.
hasDayNameSystem
Indicates that an entity employs or is associated with a particular system for naming or designating days.
- 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_69ca843170f88190800a8ab2b5fc568e |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd51be35cc8190bafad423a142c305 |
completed | April 1, 2026, 5:11 p.m. |
| PD | Predicate disambiguation | batch_69cca545b2448190a4297312e39c21ac |
completed | April 1, 2026, 4:55 a.m. |
| PDg | Predicate description generation | batch_69cca89b3368819087a3d69270c1f185 |
completed | April 1, 2026, 5:09 a.m. |
Created at: March 30, 2026, 7:46 p.m.