Triple
T11251982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Outsider |
E266339
|
entity |
| Predicate | interferesDirectly |
P91253
|
FINISHED |
| Object | rarely |
—
|
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: rarely | Statement: [The Outsider, interferesDirectly, rarely]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: interferesDirectly Context triple: [The Outsider, interferesDirectly, rarely]
-
A.
hasInterference
chosen
Indicates that one entity negatively affects or obstructs the normal function, performance, or occurrence of another entity or process.
-
B.
intervenesWhen
Indicates that one entity takes action to interrupt, mediate, or alter the course of another entity’s ongoing situation or process when certain conditions arise.
-
C.
intervenedIn
Indicates that an entity took action to alter, influence, or interrupt the course of an event, process, or interaction involving other entities.
-
D.
selfInteracts
Indicates that an entity interacts with itself, rather than with a distinct external entity.
-
E.
areAffectedBy
Indicates that one entity experiences an effect, influence, or impact as a result of another entity or event.
- 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_69d6aac7953c8190b82caf9d7640fdf9 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e933648481909873094bc89ed041 |
completed | April 9, 2026, 6 p.m. |
| PD | Predicate disambiguation | batch_69d78793c00481908a3f764b610b77a4 |
completed | April 9, 2026, 11:03 a.m. |
Created at: April 8, 2026, 9:31 p.m.