Triple
T26528478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lázaro de Tormes |
E670754
|
entity |
| Predicate | lifeCondition |
P146005
|
FINISHED |
| Object | poverty |
—
|
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: poverty | Statement: [Lázaro de Tormes, lifeCondition, poverty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lifeCondition Context triple: [Lázaro de Tormes, lifeCondition, poverty]
-
A.
lifeSituation
chosen
Indicates the general circumstances, conditions, or context in which an entity’s life currently exists or unfolds.
-
B.
lifeStatus
Indicates the current state of an entity’s existence, such as whether it is alive, dead, or in another defined life condition.
-
C.
lifeDomain
Indicates the broad biological or existential category or realm within which an entity’s life or living characteristics are classified.
-
D.
lifeDetails
Indicates that additional information or specific aspects about an entity’s life (such as background, experiences, or personal history) are being described.
-
E.
lifeCharacteristic
Indicates that an entity possesses a particular trait, feature, or quality relevant to its life or living state.
- 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_69eeb31ea1e08190b9ff43cf9bc25bf8 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f61f12b0f08190bc4a16907941864c |
completed | May 2, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69f61b3a8ae0819090189fbd8eb19f2f |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 1:33 a.m.