Triple
T16240016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ruth Stoops |
E394217
|
entity |
| Predicate | caughtIn |
P79702
|
FINISHED |
| Object | crossfire of the abortion debate |
—
|
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: crossfire of the abortion debate | Statement: [Ruth Stoops, caughtIn, crossfire of the abortion debate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: caughtIn Context triple: [Ruth Stoops, caughtIn, crossfire of the abortion debate]
-
A.
caughtBetween
chosen
Indicates being simultaneously subject to opposing forces, demands, or sides, unable to fully align with or escape either.
-
B.
trappedIn
Indicates that one entity is confined or caught within another entity or bounded space, unable to leave freely.
-
C.
trappedDuring
Indicates that one entity is confined, caught, or immobilized while a specified event or situation is occurring.
-
D.
catches
Indicates that one entity successfully seizes, intercepts, or takes hold of another entity, often stopping its motion or preventing its escape.
-
E.
heldCaptive
Indicates that one entity is being forcibly confined or restrained by another, preventing their freedom of movement or escape.
- 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_69d87f2171208190951025e526947816 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2455d5270819090171d4207223a28 |
completed | April 17, 2026, 2:36 p.m. |
| PD | Predicate disambiguation | batch_69e219ee6f6481909663b388dc99770a |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:04 a.m.