Triple
T22187492
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rome Derby |
E548332
|
entity |
| Predicate | derbyOf |
P68699
|
FINISHED |
| Object | AS Roma supporters |
—
|
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: AS Roma supporters | Statement: [Rome Derby, derbyOf, AS Roma supporters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: derbyOf Context triple: [Rome Derby, derbyOf, AS Roma supporters]
-
A.
derby
Indicates a competitive match or contest, typically between closely linked or rival entities (such as teams from the same area or group).
-
B.
derbyInvolves
chosen
Indicates that a particular derby event includes or features the participation of a specified entity or entities.
-
C.
derbyFocus
Indicates that something is the main subject, theme, or point of attention within the context of a derby event or competition.
-
D.
isDerby
Indicates that a competition or match is a derby, typically involving teams or participants from the same locality or with a strong rivalry.
-
E.
regionDerby
Indicates a competitive match or rivalry that takes place between teams or participants from the same geographic region.
- 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_69e11e3e0c7c8190b30d278845e2497e |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12aaa32288190830f6dfc626fb26a |
completed | April 28, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69e71b48576c8190a8e93738fd9cfda5 |
completed | April 21, 2026, 6:38 a.m. |
Created at: April 16, 2026, 8:35 p.m.