Triple
T4099486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Don Diego Vega |
E87903
|
entity |
| Predicate | parentalBackground |
P13742
|
FINISHED |
| Object | son of a wealthy landowner |
—
|
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: son of a wealthy landowner | Statement: [Don Diego Vega, parentalBackground, son of a wealthy landowner]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parentalBackground Context triple: [Don Diego Vega, parentalBackground, son of a wealthy landowner]
-
A.
hasFamilyBackgroundIn
chosen
Indicates that an entity comes from, or is associated with, a particular familial or ancestral background.
-
B.
parentsNationality
Indicates that it specifies the country or nationality associated with a person's parent or parents.
-
C.
parentFormation
Indicates that one geological formation serves as the larger or originating unit from which another formation is derived or classified.
-
D.
parents
Indicates a parental relationship where one entity is the mother or father of another entity.
-
E.
parentalCare
Indicates that one entity provides nurturing, protection, or support to another in a parent-like role.
- 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_69aed94564cc8190a9c1457daedb6e7f |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefd0d9c508190b8aedf83f3310513 |
completed | March 9, 2026, 5:02 p.m. |
| PD | Predicate disambiguation | batch_69aef90b2ef08190ae84febfd69dd48b |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:40 p.m.