Triple
T26000956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nikolai Lvovich Tolstoy |
E646619
|
entity |
| Predicate | land ownership |
P10159
|
FINISHED |
| Object | estates in the Russian Empire |
—
|
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: estates in the Russian Empire | Statement: [Nikolai Lvovich Tolstoy, land ownership, estates in the Russian Empire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: land ownership Context triple: [Nikolai Lvovich Tolstoy, land ownership, estates in the Russian Empire]
-
A.
landTenure
Indicates the type, conditions, or rights under which land is held, used, or owned by an entity.
-
B.
landholdings
chosen
Indicates the extent or collection of land owned, controlled, or held by an entity.
-
C.
landManagement
Indicates how land is planned, used, and controlled over time, including decisions about its conservation, development, and resource use.
-
D.
ownedLandBy
Indicates that one entity possesses legal or recognized ownership rights over a piece or area of land associated with another entity.
-
E.
Land
Indicates that an entity arrives onto and comes to rest on a surface or ground, typically from the air or another elevated position.
- 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_69e77e89d5848190b54352cdb74f6029 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f605755bd48190a760f5301eafb3ae |
completed | May 2, 2026, 2:08 p.m. |
| PD | Predicate disambiguation | batch_69f4a10728e08190bc0b96c558740f51 |
completed | May 1, 2026, 12:48 p.m. |
Created at: April 22, 2026, 9 a.m.