Triple
T17249489
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ponte San Bartolomeo |
E418711
|
entity |
| Predicate | hasLaterStyle |
P1609
|
FINISHED |
| Object | 19th-century reconstruction style |
—
|
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: 19th-century reconstruction style | Statement: [Ponte San Bartolomeo, hasLaterStyle, 19th-century reconstruction style]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLaterStyle Context triple: [Ponte San Bartolomeo, hasLaterStyle, 19th-century reconstruction style]
-
A.
hasStyle
chosen
Indicates that an entity possesses, exhibits, or is characterized by a particular style or manner.
-
B.
hasHigherStyleThan
Indicates that one entity’s style is considered superior or more fashionable than another’s.
-
C.
hasMatureStyleComparedTo
Indicates that one entity exhibits a more developed, refined, or advanced style in comparison to another entity.
-
D.
hasSystemStyle
Indicates that one entity is associated with, or characterized by, a particular system-defined style of another entity.
-
E.
hasSubstyle
Indicates that one style is a more specific or subordinate variant of another style within a hierarchical style structure.
- 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_69d886d9ab108190b70edd8d17aa1204 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42e2636f48190b29548ff80402bef |
completed | April 19, 2026, 1:21 a.m. |
| PD | Predicate disambiguation | batch_69e3832553ac819091aa917c84f755b6 |
completed | April 18, 2026, 1:12 p.m. |
Created at: April 10, 2026, 5:39 a.m.