Triple
T26400128
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Procurator General at the Hoge Raad |
E663674
|
entity |
| Predicate | worksOnLevel |
P86605
|
FINISHED |
| Object | cassation |
—
|
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: cassation | Statement: [Procurator General at the Hoge Raad, worksOnLevel, cassation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worksOnLevel Context triple: [Procurator General at the Hoge Raad, worksOnLevel, cassation]
-
A.
worksAtLevel
chosen
Indicates that an entity performs work or holds a role at a specified hierarchical or organizational level.
-
B.
worksOnFeature
Indicates that an entity is actively involved in developing, implementing, or contributing to a particular feature.
-
C.
worksFor
Indicates that one entity is employed by or performs work on behalf of another entity, typically an organization or individual.
-
D.
worksOnProgram
Indicates that an entity is actively involved in contributing effort or performing tasks on a particular program.
-
E.
worksTo
Indicates that one entity performs work or exerts effort in order to achieve, support, or contribute to another entity or outcome.
- 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_69ee883823988190b418b111be28a44a |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c1f94ac8190bc6fbc7916fc0d82 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 26, 2026, 11:31 p.m.