Triple
T5106159
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Revolutionary Tribunal |
E115098
|
entity |
| Predicate | replacedPreviousBody |
P15456
|
FINISHED |
| Object | extraordinary criminal commissions |
—
|
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: extraordinary criminal commissions | Statement: [Revolutionary Tribunal, replacedPreviousBody, extraordinary criminal commissions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacedPreviousBody Context triple: [Revolutionary Tribunal, replacedPreviousBody, extraordinary criminal commissions]
-
A.
replacedBody
Indicates that one entity has taken the place of another entity’s body, substituting it in whole or in part.
-
B.
replacedBodyType
Indicates that one body type has been substituted or superseded by another body type.
-
C.
replacedDocument
Indicates that one document has been superseded or substituted by another document.
-
D.
replacedWith
Indicates that one entity has been substituted or superseded by another entity, taking over its role, function, or position.
-
E.
replacedEntity
chosen
Indicates that one entity has been substituted for, or taken the place of, another entity in a given context.
- 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_69bd4440b3348190be1251fd8b7951f1 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd75a7c6748190b02b7c2b617c830f |
completed | March 20, 2026, 4:28 p.m. |
| PD | Predicate disambiguation | batch_69bd715fe3a8819087d3065adddba515 |
completed | March 20, 2026, 4:10 p.m. |
Created at: March 20, 2026, 1:41 p.m.