Triple
T6096677
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sala della Lupa |
E135893
|
entity |
| Predicate | isPubliclyKnownFor |
P15030
|
FINISHED |
| Object | political symbolism |
—
|
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: political symbolism | Statement: [Sala della Lupa, isPubliclyKnownFor, political symbolism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPubliclyKnownFor Context triple: [Sala della Lupa, isPubliclyKnownFor, political symbolism]
-
A.
knownIn
Indicates that an entity is recognized, acknowledged, or familiar within a particular context, domain, or group.
-
B.
reconocidaPor
Indicates that an entity is recognized, acknowledged, or honored by another entity.
-
C.
formerlyKnownFor
Indicates that an entity was previously recognized or notable for a particular role, attribute, or activity, but is no longer primarily associated with it.
-
D.
fameFor
Indicates that one entity is widely known or recognized specifically because of, or in connection with, another entity.
-
E.
alsoKnownFor
chosen
Indicates that an entity is additionally recognized or noted for another work, role, achievement, or characteristic beyond its primary association.
- 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_69c0087cd3c48190b459848c72d84eb1 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c05a9764048190ad4e9a02f9a25ab6 |
completed | March 22, 2026, 9:09 p.m. |
| PD | Predicate disambiguation | batch_69c049f5ac988190b62ba565153aaa35 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:12 p.m.