Triple
T8371719
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abwehr |
E197474
|
entity |
| Predicate | someMembersInvolvedIn |
P34269
|
FINISHED |
| Object | 20 July plot |
—
|
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: 20 July plot | Statement: [Abwehr, someMembersInvolvedIn, 20 July plot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: someMembersInvolvedIn Context triple: [Abwehr, someMembersInvolvedIn, 20 July plot]
-
A.
hasMemberInvolvedIn
chosen
Indicates that a group or collective entity has at least one of its members participating in or engaged with a specified activity, event, or situation.
-
B.
mayBeInvolvedIn
Indicates that an entity has a possible, but not certain, participation or role in a particular event, activity, or situation.
-
C.
committeeInvolved
Indicates that a committee participates in, contributes to, or is otherwise actively involved in a particular activity, decision, or process.
-
D.
hasPeopleInvolved
Indicates that certain people participate in, are associated with, or are otherwise involved in the referenced entity or event.
-
E.
hasBeenInvolvedIn
Indicates that an entity has participated in, taken part in, or been connected to a particular event, activity, or situation.
- 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_69ca82f56730819080cec5d991c76f4c |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb80a509dc81909e0ea4c66b21d84f |
completed | March 31, 2026, 8:07 a.m. |
| PD | Predicate disambiguation | batch_69cb70cd04b08190ab5f72afd22a7967 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 6:01 p.m.