Triple
T28918156
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Melfitani |
E733429
|
entity |
| Predicate | associatedWithHistoricalArea |
P13711
|
FINISHED |
| Object | Kingdom of Naples |
E14183
|
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: Kingdom of Naples | Statement: [Melfitani, associatedWithHistoricalArea, Kingdom of Naples]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithHistoricalArea Context triple: [Melfitani, associatedWithHistoricalArea, Kingdom of Naples]
-
A.
partOfHistoricalArea
Indicates that one entity is located within or belongs to a designated historical area or heritage zone.
-
B.
historicalRegionAssociation
chosen
Indicates an association where an entity is or was located in, part of, or otherwise related to a specific historical region.
-
C.
hasHistoricDistrictAssociation
Indicates a relationship in which an entity is associated with, linked to, or part of a designated historic district.
-
D.
hasLocalHistoricalAssociations
Indicates that something is connected to historically significant events, people, or developments specific to a particular locality or region.
-
E.
hasNearbyHistoricArea
Indicates that one entity is located close to another entity that is designated as a historic area.
- 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_69f05b0a5cc0819094828367ae204b70 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_6a022348ae2881908eae1be79b6f6ff6 |
completed | May 11, 2026, 6:43 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2505a0ecb4819098187b0b3f1a74a6 |
completed | June 7, 2026, 5:46 a.m. |
| PD | Predicate disambiguation | batch_6a0220beb6b08190981fb86363757517 |
completed | May 11, 2026, 6:32 p.m. |
Created at: April 28, 2026, 8:17 a.m.