Triple
T15862593
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kholm |
E384627
|
entity |
| Predicate | presentDayNameUsage |
P58651
|
FINISHED |
| Object | used mainly in East Slavic historiography |
—
|
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: used mainly in East Slavic historiography | Statement: [Kholm, presentDayNameUsage, used mainly in East Slavic historiography]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: presentDayNameUsage Context triple: [Kholm, presentDayNameUsage, used mainly in East Slavic historiography]
-
A.
presentDayNameUsedSince
Indicates that the current name of an entity has been in use since a specified point in time.
-
B.
presentDayNameOfCapital
Indicates that one entity is the current, officially used name of the capital city associated with another entity.
-
C.
dayName
Indicates the specific name of the day of the week associated with a given date or time.
-
D.
knownTodayAs
chosen
Indicates that an entity is currently referred to or recognized by a particular name or designation in the present time.
-
E.
presentDayIncludes
Indicates that the current day in a given calendar or time context encompasses or contains a specified time, date, or event.
- 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_69d86da422088190aac39e32e6c68429 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e174de2cd48190ab18e48c9f051a2a |
completed | April 16, 2026, 11:46 p.m. |
| PD | Predicate disambiguation | batch_69e142b976c081908d3ba3e705419f3a |
completed | April 16, 2026, 8:12 p.m. |
Created at: April 10, 2026, 4:50 a.m.