Triple
T35149299
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sânnicolau Mare |
E1014939
|
entity |
| Predicate | treasureHousedAt |
P36131
|
FINISHED |
| Object | Kunsthistorisches Museum, Vienna |
—
|
NE NERFINISHED |
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: Kunsthistorisches Museum, Vienna | Statement: [Sânnicolau Mare, treasureHousedAt, Kunsthistorisches Museum, Vienna]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: treasureHousedAt Context triple: [Sânnicolau Mare, treasureHousedAt, Kunsthistorisches Museum, Vienna]
-
A.
treasureOwnedBy
Indicates that a particular treasure is possessed or legally held by a specific owner.
-
B.
treasureInvolved
Indicates that a situation, event, or action involves or is related to treasure in some significant way.
-
C.
notableHeistTarget
Indicates that an entity is a significant or high-profile target of a heist or major theft.
-
D.
relicsLocatedIn
chosen
Indicates that certain relics are situated, stored, or found within a specific location.
-
E.
enshrinedWithin
Indicates that one entity is formally preserved, honored, or safeguarded inside or as part of another entity, often with a sense of protection or reverence.
- 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_69f76dda7c108190a2ffd93eb6c341a7 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78cea708c8190a2702c9825b6b094 |
completed | May 3, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69f78b9106008190930b3b3675b737d6 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 3, 2026, 4:02 p.m.