Triple
T27466144
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Data Protection Review Court |
E693181
|
entity |
| Predicate | languageUsedInProceedings |
P80867
|
FINISHED |
| Object | English |
—
|
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: English | Statement: [Data Protection Review Court, languageUsedInProceedings, English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageUsedInProceedings Context triple: [Data Protection Review Court, languageUsedInProceedings, English]
-
A.
languageOfProceedingsOverseen
chosen
Indicates the language in which the proceedings that an entity oversees or presides over are conducted.
-
B.
languagesUsed
Indicates that one entity uses, employs, or is expressed in one or more languages associated with the other entity.
-
C.
languageOfSubmissions
Indicates the language in which the submissions are written or communicated.
-
D.
officialLanguageOfProgramMaterials
Indicates the language officially used in the materials or documentation of a program.
-
E.
primaryLanguageOfPrograms
Indicates that a given language is the main programming language used to implement or develop the specified programs.
- 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_69ef538105548190a771cc5a0cf8c211 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69fd35d108908190b79b1e8e6bbd62aa |
completed | May 8, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69fd34cb46108190b43c3b7f67ec4cd4 |
completed | May 8, 2026, 12:56 a.m. |
Created at: April 27, 2026, 12:52 p.m.