Triple
T37121577
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roskilde Festival |
E919269
|
entity |
| Predicate | implementedAfter2000 |
P137670
|
FINISHED |
| Object | enhanced crowd safety measures |
—
|
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: enhanced crowd safety measures | Statement: [Roskilde Festival, implementedAfter2000, enhanced crowd safety measures]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: implementedAfter2000 Context triple: [Roskilde Festival, implementedAfter2000, enhanced crowd safety measures]
-
A.
implementedAfter
Indicates that one implementation occurs or is introduced only after another specified implementation has taken place or been completed.
-
B.
introducedAfter
Indicates that one entity was introduced at a later time or stage than another entity.
-
C.
post2000Status
chosen
Indicates whether a given entity’s status, condition, or classification applies specifically to the period after the year 2000.
-
D.
dateImplemented
Indicates the date on which something (such as a plan, rule, feature, or system) was put into effect or made operational.
-
E.
statusAfter2003
Indicates the status or condition of an entity as it exists after the year 2003.
- 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_69f76e9c57148190ba789dd059645bb9 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb344c60f8819090f2e21e1e61d621 |
completed | May 6, 2026, 12:30 p.m. |
| PD | Predicate disambiguation | batch_69fb2f642db08190b562725502c74ea6 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 4:15 p.m.