Triple
T14514156
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jesus in "El ángel exterminador" |
E340473
|
entity |
| Predicate | settingOfConfinement |
P6464
|
FINISHED |
| Object | luxurious mansion |
—
|
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: luxurious mansion | Statement: [Jesus in "El ángel exterminador", settingOfConfinement, luxurious mansion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: settingOfConfinement Context triple: [Jesus in "El ángel exterminador", settingOfConfinement, luxurious mansion]
-
A.
confinementTolerance
Indicates the degree to which an entity can endure or function effectively under restricted, enclosed, or limited-movement conditions.
-
B.
isConfined
Indicates that an entity is restricted to a limited space or area, unable to move freely beyond defined boundaries.
-
C.
restraintType
Indicates the specific kind or method of restraint applied in a given situation or relationship.
-
D.
detentionCondition
Indicates the specific terms, circumstances, or requirements under which a person is held in detention.
-
E.
placeOfDetention
chosen
Indicates the location or facility where an entity is or was held in detention.
- 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_69d822d9c0408190b9a2b3643e58bb4d |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69de9a6d82988190b6f957012bcc63d4 |
completed | April 14, 2026, 7:50 p.m. |
| PD | Predicate disambiguation | batch_69de5c4ccba08190a988bfda0bc9f5cb |
completed | April 14, 2026, 3:25 p.m. |
Created at: April 10, 2026, 1:21 a.m.