Triple
T23675647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Сорочинці |
E584864
|
entity |
| Predicate | історичноВідомеЗ |
P65445
|
FINISHED |
| Object | XVII століття |
—
|
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: XVII століття | Statement: [Сорочинці, історичноВідомеЗ, XVII століття]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: історичноВідомеЗ Context triple: [Сорочинці, історичноВідомеЗ, XVII століття]
-
A.
историческийПредок
Indicates that one entity is a historical ancestor of another, existing in an earlier time and belonging to its lineage.
-
B.
historicalSee
Indicates that one entity observed, encountered, or took visual notice of another entity in the past.
-
C.
featuresHistorian
Indicates that something includes or presents a historian as a notable participant, subject, or element.
-
D.
historicFor
chosen
Indicates that something holds historical significance or importance specifically in relation to another entity.
-
E.
historicalReference
Indicates that one entity refers to, cites, or alludes to another entity from an earlier time or historical context.
- 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_69e24901f7c08190909fd727632e823d |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b4f2e35c8190ada29694e2cbed37 |
completed | April 29, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f118dd13008190a8799b4e9cadbd79 |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:51 p.m.