Triple
T33443840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sannio DOC |
E856436
|
entity |
| Predicate | notableTownInArea |
P14082
|
FINISHED |
| Object | Benevento |
E204110
|
NE 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: Benevento | Statement: [Sannio DOC, notableTownInArea, Benevento]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableTownInArea Context triple: [Sannio DOC, notableTownInArea, Benevento]
-
A.
notableHumanSettlement
Indicates that a location is recognized as a significant or noteworthy human settlement, such as a city, town, or village.
-
B.
hasNotableTown
chosen
Indicates that an entity includes or is associated with a town that is considered notable or significant in some way.
-
C.
notableRegionOfSettlement
Indicates that a specified region is a significant or prominent place where an entity is or has been settled.
-
D.
notableReservationTown
Indicates that a town is notably associated with or recognized for a particular reservation.
-
E.
notableInCity
Indicates that an entity is particularly prominent, recognized, or significant within a specific city.
- F. None of above.
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_69f34971b75881908be360bb041f003c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3819bc913c8190b9622ba8cb3cf862 |
completed | June 21, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_6a0379f505c88190ac0879ab422c3054 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:37 a.m.