Triple
T38056971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | De Klassieker |
E950230
|
entity |
| Predicate | policingLevel |
P33005
|
FINISHED |
| Object | high |
—
|
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: high | Statement: [De Klassieker, policingLevel, high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: policingLevel Context triple: [De Klassieker, policingLevel, high]
-
A.
lawEnforcementLevel
chosen
Indicates the degree or intensity of law enforcement presence, activity, or strictness applied in a given context.
-
B.
policingModel
Indicates the approach, strategy, or framework used to organize and conduct policing activities or law enforcement operations.
-
C.
areaTypePoliced
Indicates that a particular type of geographic or administrative area falls under the policing responsibility or jurisdiction of a specified policing entity.
-
D.
lawEnforcementAgencyLevel
Indicates the jurisdictional or administrative level at which a law enforcement agency operates (e.g., local, regional, national).
-
E.
policePresence
Indicates that law enforcement officers are present at or monitoring a particular location, event, or situation.
- 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_69f76f01e63c819093b6012fc974f35a |
completed | May 3, 2026, 3:51 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: May 3, 2026, 4:21 p.m.