Triple
T18428605
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La Condená |
E450203
|
entity |
| Predicate | causeOfState |
P82638
|
FINISHED |
| Object | condemnation for sins |
—
|
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: condemnation for sins | Statement: [La Condená, causeOfState, condemnation for sins]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeOfState Context triple: [La Condená, causeOfState, condemnation for sins]
-
A.
causeOf
Indicates that one entity brings about, produces, or is responsible for the occurrence or existence of another entity or event.
-
B.
statehoodContext
Indicates the contextual circumstances, conditions, or framework under which an entity’s status as a state (or its statehood) is defined, recognized, or discussed.
-
C.
causeStatus
chosen
Indicates that one entity brings about, initiates, or is responsible for a particular state or condition in another entity.
-
D.
foundingState
Indicates that a state or entity played a primary role in establishing or creating another organization, institution, or political entity.
-
E.
statehoodEvent
Indicates an event or process through which an entity attains, changes, or loses the status of being a recognized 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_69d8d381d6388190a9e94e9c658174e4 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e51b14c4d481909af975575a43c4e1 |
completed | April 19, 2026, 6:12 p.m. |
| PD | Predicate disambiguation | batch_69e469bf7f74819096a01173493412c2 |
completed | April 19, 2026, 5:35 a.m. |
Created at: April 10, 2026, 11:25 a.m.