Triple
T24202187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St. Michael's Church, Vienna |
E600009
|
entity |
| Predicate | hasCryptFeature |
P182
|
FINISHED |
| Object | naturally mummified bodies |
—
|
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: naturally mummified bodies | Statement: [St. Michael's Church, Vienna, hasCryptFeature, naturally mummified bodies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCryptFeature Context triple: [St. Michael's Church, Vienna, hasCryptFeature, naturally mummified bodies]
-
A.
hasCrypt
Indicates that one entity possesses, contains, or is associated with a crypt belonging to or located within it.
-
B.
hasCryptUse
Indicates that an entity makes use of cryptographic methods, protocols, or mechanisms in its operation or behavior.
-
C.
supportsHardwareCryptography
Indicates that one entity provides or enables hardware-based cryptographic operations or capabilities for another entity.
-
D.
hasFeature
chosen
Indicates that an entity possesses, exhibits, or includes a particular characteristic, attribute, or component.
-
E.
hasSecurityExtension
Indicates that an entity is associated with, or equipped with, an additional component or feature that enhances its security.
- 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_69e288ceaab88190899d0acb5931591d |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f27ca2d6708190ba20d00870d0af49 |
completed | April 29, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f1c43e55688190b55fc20274ed471c |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 17, 2026, 11:36 p.m.