Triple
T26909765
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Casertana |
E677357
|
entity |
| Predicate | hasHomeDerby |
P176591
|
FINISHED |
| Object | Campania regional derbies |
—
|
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: Campania regional derbies | Statement: [Casertana, hasHomeDerby, Campania regional derbies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHomeDerby Context triple: [Casertana, hasHomeDerby, Campania regional derbies]
-
A.
hasHomeDerbyFor
Indicates that one entity serves as the home venue or location where another entity’s derby event is held.
-
B.
hasHomeStadiumInDerby
Indicates that an entity’s home stadium is located in the city or area of Derby.
-
C.
hasHomeStadiumContext
Indicates that an entity’s home stadium is specified or characterized within a particular contextual framework (such as time, competition, or role).
-
D.
hasHomeGameSite
Indicates that an entity’s designated location for hosting its home games is another specified entity (the home game site).
-
E.
isDerbyIn
chosen
Indicates that a derby (typically a sports match or rivalry game) takes place within or belongs to a particular location or competition context.
- 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_69eee9bcef1c8190be88586bb902bb9b |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f6f8565134819096aac0175f924a9f |
completed | May 3, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f6f65fd1d08190b88e5e68ba268500 |
completed | May 3, 2026, 7:16 a.m. |
Created at: April 27, 2026, 6:01 a.m.