Triple
T3106164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prosecutor v. Thomas Lubanga Dyilo |
E64834
|
entity |
| Predicate | proceduralFeature |
P5048
|
FINISHED |
| Object | extensive victim participation in proceedings |
—
|
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: extensive victim participation in proceedings | Statement: [Prosecutor v. Thomas Lubanga Dyilo, proceduralFeature, extensive victim participation in proceedings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: proceduralFeature Context triple: [Prosecutor v. Thomas Lubanga Dyilo, proceduralFeature, extensive victim participation in proceedings]
-
A.
processFeature
Indicates that an entity performs or undergoes an operation that handles, transforms, or otherwise acts upon a specific feature.
-
B.
createdFeature
Indicates that one entity brought another entity into existence or caused it to be produced as a feature.
-
C.
engineeringFeature
Indicates that one entity serves as an engineering-related feature, component, or characteristic of another entity within a technical or designed system.
-
D.
featureType
chosen
Indicates the specific kind or category of feature that characterizes or distinguishes an entity.
-
E.
previousDesignFeature
Indicates that one design feature precedes another in a sequence or earlier version of a design.
- 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_69ad857eeaf48190b34ebfdaa7a264cf |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada29beff08190b6e1eb6b0608d0eb |
completed | March 8, 2026, 4:23 p.m. |
| PD | Predicate disambiguation | batch_69ad9df25d4c81908ff0f6cff55d0563 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:04 p.m.