Triple
T38167986
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Лицейский сад |
E953199
|
entity |
| Predicate | историческийПериодФормирования |
P74212
|
FINISHED |
| Object | XIX век |
—
|
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: XIX век | Statement: [Лицейский сад, историческийПериодФормирования, XIX век]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: историческийПериодФормирования Context triple: [Лицейский сад, историческийПериодФормирования, XIX век]
-
A.
historicalFormation
Indicates the process or circumstances through which something came into existence or took shape over time in history.
-
B.
historicalPeriodOfCurrentForm
chosen
Indicates the historical period during which the entity’s current form, structure, or configuration came into existence or was established.
-
C.
historicallyFormed
Indicates that the relationship or structure arose or developed through historical processes rather than being newly created or purely theoretical.
-
D.
historicalIntroductionPeriod
Indicates the time period during which something was first introduced or came into use in a historical context.
-
E.
historicalForm
Indicates that one entity is an earlier or historically attested form or variant of another entity.
- 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_69f76f0b93c48190a117319ab3a9f282 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fcc42cbac48190b8d3e4c9ce140838 |
completed | May 7, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69fcb0fc69c88190800453eb57a7e62c |
completed | May 7, 2026, 3:34 p.m. |
Created at: May 3, 2026, 4:21 p.m.