Triple
T37926617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Comune di Anfo |
E946109
|
entity |
| Predicate | hasHistoricMilitaryStructure |
P19823
|
FINISHED |
| Object | Rocca d’Anfo |
E2249174
|
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: Rocca d’Anfo | Statement: [Comune di Anfo, hasHistoricMilitaryStructure, Rocca d’Anfo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricMilitaryStructure Context triple: [Comune di Anfo, hasHistoricMilitaryStructure, Rocca d’Anfo]
-
A.
historicalStructure
chosen
Indicates that the subject is a structure recognized for its historical significance or heritage value.
-
B.
hasMilitarySignificanceSince
Indicates that something has held military importance or strategic value starting from a specified point in time.
-
C.
hasNearbyMilitaryHistorySite
Indicates that an entity is located close to a site of historical military significance, such as a battlefield, fort, or memorial.
-
D.
militaryArchitecture
Indicates a relationship where something is designed, built, or characterized specifically for military defensive or fortification purposes.
-
E.
hasMilitarySignificance
Indicates that something holds strategic or tactical importance for military planning, operations, or defense objectives.
- 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_69f76ef3b7248190892fb9706423be7c |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69ffac35ac5481908b6bdfd5bbe8c76e |
completed | May 9, 2026, 9:50 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a415d1e75a881909d0706a77854f10a |
completed | June 28, 2026, 5:42 p.m. |
| PD | Predicate disambiguation | batch_69ffabbfd2548190964c851496bbbaee |
completed | May 9, 2026, 9:48 p.m. |
Created at: May 3, 2026, 4:20 p.m.