Triple
T18090340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jean de Voilemont |
E432946
|
entity |
| Predicate | bearerRoleInEvent |
P4073
|
FINISHED |
| Object | perpetrator of espionage in the Dreyfus Affair |
—
|
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: perpetrator of espionage in the Dreyfus Affair | Statement: [Jean de Voilemont, bearerRoleInEvent, perpetrator of espionage in the Dreyfus Affair]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bearerRoleInEvent Context triple: [Jean de Voilemont, bearerRoleInEvent, perpetrator of espionage in the Dreyfus Affair]
-
A.
eventRole
chosen
Indicates the specific function, capacity, or part an entity plays within an event or occurrence.
-
B.
accessibleForEventType
Indicates that something can be used, reached, or is available in the context of a specified type or category of event.
-
C.
associatedWithRoleOfNameBearer
Indicates that an entity is connected to or involved with the specific role or function held by a designated name bearer.
-
D.
eventParticipant
Indicates that an entity takes part in, is involved in, or participates in a particular event.
-
E.
antRole
Indicates that one entity has a specific role, function, or responsibility in relation to another entity.
- 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_69d8b907d05c819083cc3bd6021089e6 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4dd17ba98819085a15e8593d98259 |
completed | April 19, 2026, 1:48 p.m. |
| PD | Predicate disambiguation | batch_69e4330e1f2881908b2506d47c48736b |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:27 a.m.