Triple
T33413439
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eclanum, Campania |
E855648
|
entity |
| Predicate | hasNearbyModernMunicipality |
P132960
|
FINISHED |
| Object | Mirabella Eclano |
—
|
NE NERFINISHED |
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: Mirabella Eclano | Statement: [Eclanum, Campania, hasNearbyModernMunicipality, Mirabella Eclano]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyModernMunicipality Context triple: [Eclanum, Campania, hasNearbyModernMunicipality, Mirabella Eclano]
-
A.
hasModernNearbyCity
chosen
Indicates that an entity is located near or in proximity to a contemporary, currently existing city.
-
B.
hasMunicipalitySeatNearby
Indicates that the municipality’s administrative seat is located in close proximity to the referenced place or entity.
-
C.
isMunicipalityNear
Indicates that one municipality is located close to another municipality or geographic reference point.
-
D.
locatedInPresentDayMunicipality
Indicates that an entity is situated within the boundaries of a specific municipality as it exists in the present day, regardless of historical administrative changes.
-
E.
hasNearbyCityFunction
Indicates that one entity serves as a nearby urban center or city-like service hub for 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_69f3496f04a08190804e56ac5098b8e4 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff795d25d08190b7584c72be39d309 |
completed | May 9, 2026, 6:13 p.m. |
| PD | Predicate disambiguation | batch_69ff78a90fbc8190a62c57456dc1d4ad |
completed | May 9, 2026, 6:10 p.m. |
Created at: May 1, 2026, 1:36 a.m.