Triple
T32562664
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russian History from the Most Ancient Times |
E832268
|
entity |
| Predicate | usesChronicle |
P41120
|
FINISHED |
| Object | Primary Chronicle |
—
|
NE NERFINISHED |
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: Primary Chronicle | Statement: [Russian History from the Most Ancient Times, usesChronicle, Primary Chronicle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesChronicle Context triple: [Russian History from the Most Ancient Times, usesChronicle, Primary Chronicle]
-
A.
chronicleScope
Indicates the temporal or contextual span over which an event, process, or narrative is recorded or documented.
-
B.
chronicledBy
chosen
Indicates that something is documented, recorded, or described in detail by a particular source, author, or record.
-
C.
chronicleFocus
Indicates that something serves as the primary subject, theme, or emphasis within a chronicle or narrative account.
-
D.
chronologyUsedBy
Indicates that a particular system, method, or scheme of chronological ordering is employed or adopted by a given entity.
-
E.
chronologyOf
Indicates that one entity represents the temporal ordering, sequence, or historical timeline of events or states associated with 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_69f34926b9848190ace47d2dd0a0de7c |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fd3d46d1f48190a1b20dd063224b7d |
completed | May 8, 2026, 1:32 a.m. |
| PD | Predicate disambiguation | batch_69fd3ae1510c81908fe1280efc17feee |
completed | May 8, 2026, 1:22 a.m. |
Created at: May 1, 2026, 1:03 a.m.