Triple
T18846592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siebold incident |
E460931
|
entity |
| Predicate | natureOfAccusation |
P873
|
FINISHED |
| Object | espionage-related activities |
—
|
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: espionage-related activities | Statement: [Siebold incident, natureOfAccusation, espionage-related activities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: natureOfAccusation Context triple: [Siebold incident, natureOfAccusation, espionage-related activities]
-
A.
accusationType
chosen
Indicates the specific category or nature of an accusation made by one party against another.
-
B.
accusationDescription
Indicates that a statement or explanation is being provided that details the nature, content, or specifics of an accusation made by one party against another.
-
C.
accusedOf
Indicates that one entity has formally alleged or claimed that another entity committed a specific wrongdoing or offense.
-
D.
accusedIn
Indicates that a person or entity is formally charged with wrongdoing in a particular case, proceeding, or context.
-
E.
victimOfAccusation
Indicates that an entity is the target or subject of an accusation made by another party.
- 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_69d8dcfa11e4819090ab1ef5bdcd2b2e |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5b8efafdc81909608b8a47deeaa8e |
completed | April 20, 2026, 5:26 a.m. |
| PD | Predicate disambiguation | batch_69e48d1e7dac81909ea1e758c87773c5 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:56 a.m.