Triple
T30892730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | De Lacey family |
E786944
|
entity |
| Predicate | causeOfPoverty |
P694
|
FINISHED |
| Object | political persecution |
—
|
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: political persecution | Statement: [De Lacey family, causeOfPoverty, political persecution]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeOfPoverty Context triple: [De Lacey family, causeOfPoverty, political persecution]
-
A.
causeOfMarginalization
Indicates a factor, action, or condition that contributes to the social, economic, or political marginalization of an entity.
-
B.
causeOfDownfall
Indicates a factor, event, or agent that brings about the failure, ruin, or collapse of someone or something.
-
C.
isResourcePoor
Indicates that an entity lacks sufficient resources (such as money, materials, or capacity) to meet its needs or perform effectively.
-
D.
hasWealthVsPovertyTheme
Indicates that the relationship or situation prominently involves contrasts or dynamics between wealth and poverty as a central theme.
-
E.
causeOf
chosen
Indicates that one entity brings about, produces, or is responsible for the occurrence or existence of another entity or event.
- 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_69f224bbfa7c81908448e0c261c523e3 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7764ab1fc81909f9348db87bd7692 |
completed | May 3, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69f76905d9c88190b1ee810bc9ab644f |
completed | May 3, 2026, 3:25 p.m. |
Created at: April 29, 2026, 8:49 p.m.