Triple
T30907861
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lupita Ramos |
E787352
|
entity |
| Predicate | kidnappingIsCentralPlot |
P170286
|
FINISHED |
| Object | Man on Fire |
—
|
NE NERFINISHED |
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: Man on Fire | Statement: [Lupita Ramos, kidnappingIsCentralPlot, Man on Fire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: kidnappingIsCentralPlot Context triple: [Lupita Ramos, kidnappingIsCentralPlot, Man on Fire]
-
A.
kidnappedIn
Indicates that an entity was forcibly taken or abducted within, or as part of an event occurring in, a specified location or context.
-
B.
wasKidnapped
Indicates that an entity was forcibly taken and held against their will by another entity.
-
C.
oftenKidnaps
Indicates that one entity frequently or habitually kidnaps another entity.
-
D.
abductedIn
Indicates that an entity was forcibly taken or kidnapped at or during a specified time or event.
-
E.
abductedFrom
Indicates that an entity was forcibly taken away or kidnapped from a specified location or source.
- 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_69f224be300c8190a6513ce1ee0a7026 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69281097081908756e0720f537ba1 |
completed | May 3, 2026, 12:10 a.m. |
| PD | Predicate disambiguation | batch_69f68b7ec098819080480998038de940 |
completed | May 2, 2026, 11:40 p.m. |
| PDg | Predicate description generation | batch_69f68c517f308190873c1c7e05a0c6d0 |
completed | May 2, 2026, 11:44 p.m. |
Created at: April 29, 2026, 8:50 p.m.