Triple
T9124119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bakunin family estate |
E218929
|
entity |
| Predicate | propertyForm |
P87216
|
FINISHED |
| Object | hereditary estate |
—
|
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: hereditary estate | Statement: [Bakunin family estate, propertyForm, hereditary estate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: propertyForm Context triple: [Bakunin family estate, propertyForm, hereditary estate]
-
A.
property
Indicates that one entity possesses, is characterized by, or has an attribute or quality associated with another entity.
-
B.
housingForm
Indicates the type or structure of housing associated with an entity (e.g., apartment, single-family home, dormitory).
-
C.
squareProperty
Indicates that one entity is the square (second power) of a numerical property or value associated with another entity.
-
D.
architectureProperty
Indicates that a specified architectural characteristic or feature is attributed to, or associated with, an entity.
-
E.
builtProperty
Indicates that a constructed structure or building has been created on, or is associated with, a particular property or piece of land.
- F. None of above. chosen
Provenance (4 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_69ca83dddd548190983b96c664f7f367 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca8b7436c8190b45bc6e4d6ec7066 |
completed | April 1, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69cc66003e3c819091e1e42c9cf7c781 |
completed | April 1, 2026, 12:25 a.m. |
| PDg | Predicate description generation | batch_69cc6a3c78388190a7436acc0e44ff55 |
completed | April 1, 2026, 12:43 a.m. |
Created at: March 30, 2026, 7:17 p.m.