Triple
T1498266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flick Trial |
E29735
|
entity |
| Predicate | resultForFriedrichFlick |
P28513
|
FINISHED |
| Object | convicted |
—
|
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: convicted | Statement: [Flick Trial, resultForFriedrichFlick, convicted]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resultForFriedrichFlick Context triple: [Flick Trial, resultForFriedrichFlick, convicted]
-
A.
resultForDutchRepublic
Indicates the outcome or consequence that pertains specifically to the Dutch Republic in a given event or context.
-
B.
result
Indicates that one entity is produced, caused, or brought about as an outcome or consequence of another entity or process.
-
C.
foundedAsResultOf
Indicates that one entity was established or created as a direct consequence or outcome of another event, action, or circumstance.
-
D.
resultDetermination
Indicates the process or criteria by which an outcome, decision, or result is established or concluded from given inputs or conditions.
-
E.
FrederickAssessment
Indicates that an entity (typically Frederick) performs, records, or is associated with an evaluation or assessment of another entity or situation.
- F. None of above. chosen
Provenance (4 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_69a498dba1d8819093b46a3a8d2485f1 |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c6ef5ce88190a6b520525a6d42a3 |
completed | March 1, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69a4c48a8cf48190a6ebf8d44a608a06 |
completed | March 1, 2026, 10:58 p.m. |
| PDg | Predicate description generation | batch_69a4c4feea448190b2b5071b28a5b608 |
completed | March 1, 2026, 11 p.m. |
Created at: March 1, 2026, 8:12 p.m.