Triple
T24681053
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NAC Breda |
E611129
|
entity |
| Predicate | hasCityDerby |
P46046
|
FINISHED |
| Object | Derby with RBC Roosendaal |
—
|
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: Derby with RBC Roosendaal | Statement: [NAC Breda, hasCityDerby, Derby with RBC Roosendaal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCityDerby Context triple: [NAC Breda, hasCityDerby, Derby with RBC Roosendaal]
-
A.
cityDerby
Indicates a competitive or rivalry relationship between two cities, often in sports or similar local contests.
-
B.
rivalryInvolvesCity
chosen
Indicates that a rivalry relationship includes or is associated with a particular city as one of its involved locations.
-
C.
cityDerbyHosted
Indicates that a particular city served as the host location for a specified derby event.
-
D.
cityDerbyName
Indicates that a city is known by a particular derby (rivalry match) name.
-
E.
hasLocalRivalry
Indicates that there is an ongoing competitive or adversarial relationship between entities that are geographically close or share the same local area.
- 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_69e2c4d5c2dc8190ac857dea25ec6ce9 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f41011d8048190be70329ba0bfb7c7 |
completed | May 1, 2026, 2:29 a.m. |
| PD | Predicate disambiguation | batch_69f40ed9d47881909fcfc0d04e8d074a |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 3:10 a.m.