Triple
T29592300
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gaius Antonius Hybrida |
E754198
|
entity |
| Predicate | removedFromOfficeFor |
P3900
|
FINISHED |
| Object | extortion in Macedonia |
—
|
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: extortion in Macedonia | Statement: [Gaius Antonius Hybrida, removedFromOfficeFor, extortion in Macedonia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: removedFromOfficeFor Context triple: [Gaius Antonius Hybrida, removedFromOfficeFor, extortion in Macedonia]
-
A.
removedFromOfficeDate
Indicates the date on which an individual was officially removed or dismissed from holding a particular office or position.
-
B.
removedFromPublicDuties
Indicates that an entity has been taken out of roles or responsibilities that involve serving or representing the public.
-
C.
removedFrom
Indicates that one entity has been taken away, extracted, or detached from another entity or context.
-
D.
separatedFromOffice
chosen
Indicates that an individual has been removed or dismissed from holding a particular office or official position.
-
E.
retiredFrom
Indicates that an entity has permanently stopped working for or being active in a specified organization, role, or activity.
- 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_69f0ef836ac88190bd809dc58b5ec907 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f66db3fdb481909b90ad0a24aaa005 |
completed | May 2, 2026, 9:33 p.m. |
| PD | Predicate disambiguation | batch_69f6659d36208190b01412600a4ed57d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 6:15 p.m.