Triple
T3764725
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mama Elena |
E82641
|
entity |
| Predicate | continuesToControl |
P50835
|
FINISHED |
| Object | Tita even after death |
—
|
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: Tita even after death | Statement: [Mama Elena, continuesToControl, Tita even after death]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: continuesToControl Context triple: [Mama Elena, continuesToControl, Tita even after death]
-
A.
canControl
Indicates that one entity has the ability or authority to direct, manage, or influence the behavior or state of another entity.
-
B.
successorControl
Indicates that control, authority, or responsibility is transferred from one entity to another that follows it in a sequence or succession.
-
C.
continuesToHost
Indicates that an entity remains the host of another entity or event over an ongoing period of time.
-
D.
usedToControl
Indicates that one entity employed another as a means or tool to exercise control or regulation over something.
-
E.
controlledAfter
Indicates that one entity gains or maintains control over another entity only after a specified time, event, or condition has occurred.
- F. None of above. chosen
Provenance (4 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_69ad8b207b0081909d2b48843fbd8795 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcbfd4be481908242c460a3f00c56 |
completed | March 8, 2026, 7:20 p.m. |
| PD | Predicate disambiguation | batch_69adc04c851c8190ae5eaebf36df539b |
completed | March 8, 2026, 6:30 p.m. |
| PDg | Predicate description generation | batch_69adc0fe3e3c8190bd886c7745c172a0 |
completed | March 8, 2026, 6:33 p.m. |
Created at: March 8, 2026, 3:35 p.m.