Triple
T17112978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fossanova |
E415270
|
entity |
| Predicate | nearbySiteArchitecturalStyle |
P52857
|
FINISHED |
| Object | Romanesque |
—
|
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: Romanesque | Statement: [Fossanova, nearbySiteArchitecturalStyle, Romanesque]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbySiteArchitecturalStyle Context triple: [Fossanova, nearbySiteArchitecturalStyle, Romanesque]
-
A.
hasBuildingStyleInSurroundings
chosen
Indicates that an entity is surrounded by or located in an area characterized by a particular building style.
-
B.
typicalNearbyLandmarks
Indicates that certain landmarks are commonly found in the vicinity of a given place or location.
-
C.
notableNearbySite
Indicates that one entity is a significant or noteworthy site located close to another entity.
-
D.
architecturalStyle
Indicates the architectural design tradition, movement, or style that characterizes the form and appearance of a structure or built work.
-
E.
nearbyHistoricalServiceFor
Indicates that a historical service or facility is located close to a given reference entity or location.
- 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_69d886d090cc8190a39cb94992586905 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3e8033840819083e9a506e48c31b4 |
completed | April 18, 2026, 8:22 p.m. |
| PD | Predicate disambiguation | batch_69e35d6b1b988190a8d6b6fe78c35e59 |
completed | April 18, 2026, 10:31 a.m. |
Created at: April 10, 2026, 5:35 a.m.