Triple
T28467282
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Shepelevychi |
E720327
|
entity |
| Predicate | hasLanguageOfHistoriography |
P30358
|
FINISHED |
| Object | Polish |
—
|
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: Polish | Statement: [Battle of Shepelevychi, hasLanguageOfHistoriography, Polish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLanguageOfHistoriography Context triple: [Battle of Shepelevychi, hasLanguageOfHistoriography, Polish]
-
A.
historicalLanguageOfScholarship
Indicates that a language has historically been used as a primary medium of scholarly, academic, or learned communication for a given community, region, or tradition.
-
B.
historicalLanguage
Indicates that one language is a historical or earlier form/ancestor of another language.
-
C.
languageOfHistoricalRecord
chosen
Indicates the language in which a given historical record is written or recorded.
-
D.
roleInLanguageHistory
Indicates the specific function, influence, or contribution an entity has had within the historical development or evolution of a language.
-
E.
inHistoriography
Indicates a relationship where something is discussed, interpreted, or treated within the field or discourse of historiography.
- 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_69f01a58a67c819097936d9e8da8d6e6 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69fcdf2394748190b35cead3e208447d |
completed | May 7, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe344ec8190a0471911952f4b82 |
completed | May 7, 2026, 6:37 p.m. |
Created at: April 28, 2026, 2:45 a.m.