Triple
T25330203
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Benevento Calcio |
E635127
|
entity |
| Predicate | cityIsKnownFor |
P24465
|
FINISHED |
| Object | witch folklore (streghe) |
—
|
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: witch folklore (streghe) | Statement: [Benevento Calcio, cityIsKnownFor, witch folklore (streghe)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cityIsKnownFor Context triple: [Benevento Calcio, cityIsKnownFor, witch folklore (streghe)]
-
A.
primaryCityLandmarkOf
Indicates that a landmark is a principal or defining landmark associated with a specific city.
-
B.
cityRecognizedBy
Indicates that a city has been formally acknowledged, certified, or granted status by a particular authority, organization, or governing body.
-
C.
cityAssociatedWith
chosen
Indicates that there is a notable connection or relationship between a city and another entity, such as relevance, involvement, or contextual association.
-
D.
isInTownKnownFor
Indicates that one entity is located in a town that is notable or distinguished for the other entity.
-
E.
cityIs
Indicates that one entity is a city associated with, or identified as, another entity.
- 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_69e75a9908108190a95427a97020632a |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f497c44c9c81909c8b56ae6693a75e |
completed | May 1, 2026, 12:08 p.m. |
| PD | Predicate disambiguation | batch_69f45d06d0388190b36ecde92013624a |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 21, 2026, 1:30 p.m.