Triple
T30491018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Derby della Scala |
E775863
|
entity |
| Predicate | intraCityDerby |
P169498
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Derby della Scala, intraCityDerby, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intraCityDerby Context triple: [Derby della Scala, intraCityDerby, true]
-
A.
cityDerby
Indicates a competitive or rivalry relationship between two cities, often in sports or similar local contests.
-
B.
cityRivalry
Indicates a competitive or adversarial relationship that exists between two cities, often involving sports, economics, culture, or historical tensions.
-
C.
cityDerbyHosted
Indicates that a particular city served as the host location for a specified derby event.
-
D.
localCompetition
Indicates that two entities are competing with each other within the same local or geographically limited market or area.
-
E.
cityDerbyName
Indicates that a city is known by a particular derby (rivalry match) name.
- F. None of above. chosen
Provenance (4 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_69f22497f91c8190afa7165bc900accd |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68749698c8190bca5e3501e053eb7 |
completed | May 2, 2026, 11:22 p.m. |
| PD | Predicate disambiguation | batch_69f678d2196c8190b9d0d2fcd47cc539 |
completed | May 2, 2026, 10:21 p.m. |
| PDg | Predicate description generation | batch_69f67d31cc60819084f64bd056e1ea4d |
completed | May 2, 2026, 10:39 p.m. |
Created at: April 29, 2026, 8:13 p.m.