Triple
T1079705
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pierre Bezukhov |
E23918
|
entity |
| Predicate | inheritsWealth |
P23690
|
FINISHED |
| Object | Large fortune |
—
|
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: Large fortune | Statement: [Pierre Bezukhov, inheritsWealth, Large fortune]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inheritsWealth Context triple: [Pierre Bezukhov, inheritsWealth, Large fortune]
-
A.
richIn
Indicates that something contains a high amount or concentration of a particular substance, quality, or resource.
-
B.
associatedHeir
Indicates that one entity is designated or recognized as the heir connected to, or inheriting from, another entity.
-
C.
hadEstate
Indicates that an entity possessed or owned a particular estate or landed property.
-
D.
inheritedFrom
Indicates that one entity has received or derived something (such as traits, rights, or property) from another entity, typically a predecessor or ancestor.
-
E.
heirOf
Indicates that one entity is the legal or designated successor who inherits from another entity, typically upon that entity’s death or transfer of rights.
- 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_69a493f1ddf48190a99d54b00e99f8ce |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b94509d08190964509ea4a2d7912 |
completed | March 1, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69a4b73d9f08819093668104f129840e |
completed | March 1, 2026, 10:01 p.m. |
| PDg | Predicate description generation | batch_69a4b80f0fb08190a19a50e38ae8f16c |
completed | March 1, 2026, 10:05 p.m. |
Created at: March 1, 2026, 7:42 p.m.