Triple
T1930100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Otto |
E40924
|
entity |
| Predicate | thematicRole |
P11527
|
FINISHED |
| Object | depicts brutality of war |
—
|
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: depicts brutality of war | Statement: [Otto, thematicRole, depicts brutality of war]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: thematicRole Context triple: [Otto, thematicRole, depicts brutality of war]
-
A.
role
Indicates the function, position, or responsibility that one entity holds in relation to another within a given context.
-
B.
semanticRelation
Indicates a general meaning-based connection between two entities, such as similarity, implication, or conceptual association.
-
C.
roleInText
chosen
Indicates that an entity participates in a text with a specific function or capacity (e.g., author, editor, character).
-
D.
aspect
Indicates a specific temporal phase or manner in which an action, event, or state unfolds or is viewed (e.g., ongoing, completed, habitual).
-
E.
grammaticalPerson
Indicates the grammatical role of a participant in speech (such as first, second, or third person) in relation to the speaker and listener.
- 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_69a8864711648190b07bed24ed76258e |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb266dcb4819090be83556615d0db |
completed | March 7, 2026, 5:06 a.m. |
| PD | Predicate disambiguation | batch_69abafeec6f881909d47acb966683279 |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:35 p.m.