Triple
T30221148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | censor (Roman Republic) |
E768346
|
entity |
| Predicate | couldExpelFrom |
P46695
|
FINISHED |
| Object | Senate |
—
|
NE NERFINISHED |
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: Senate | Statement: [censor (Roman Republic), couldExpelFrom, Senate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: couldExpelFrom Context triple: [censor (Roman Republic), couldExpelFrom, Senate]
-
A.
expelledFrom
Indicates that an entity has been formally forced to leave or is removed from a place, organization, or institution, typically as a punishment or disciplinary action.
-
B.
requestedExpulsionOf
Indicates that one entity formally asked an authority or relevant body to expel or remove another entity from a group, place, or organization.
-
C.
expelledTo
Indicates that an entity has been formally forced to leave one place, organization, or group and sent to another specified location.
-
D.
expulsionReason
Indicates the cause or justification for which an entity was expelled from a group, place, or institution.
-
E.
expel
chosen
Indicates forcing an entity to leave or be removed from a place, group, or situation, typically as a punishment or consequence.
- 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_69f2247fd8b8819087fcf83cb7a05eb8 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68a16debc8190a12f5f65ced055d7 |
completed | May 2, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69f6860def1c81909d79e1f088c4b5e5 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 7:35 p.m.