Triple
T8373431
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Stonehouse |
E197513
|
entity |
| Predicate | allegedToBe |
P16813
|
FINISHED |
| Object | Czechoslovak intelligence agent |
—
|
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: Czechoslovak intelligence agent | Statement: [John Stonehouse, allegedToBe, Czechoslovak intelligence agent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allegedToBe Context triple: [John Stonehouse, allegedToBe, Czechoslovak intelligence agent]
-
A.
allegedStatus
chosen
Indicates that a particular status or condition is claimed or asserted about an entity, but has not been confirmed as true.
-
B.
allegedActor
Indicates that the subject is claimed or accused to be the actor responsible for a particular action or event, without confirming that the claim is true.
-
C.
allegedAgentOf
Indicates that one entity is claimed or suspected, but not confirmed, to be the agent responsible for an action or event involving another entity.
-
D.
allegedAction
Indicates that an action is claimed or asserted to have occurred, typically without being proven or confirmed.
-
E.
allegedImpostor
Indicates that one entity is claimed or suspected to be fraudulently posing as 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_69ca82f56730819080cec5d991c76f4c |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb80a7cab881909d8cca66a340dceb |
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.