Triple
T23654917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Urbino Cathedral |
E584269
|
entity |
| Predicate | containsCrypt |
P5511
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Urbino Cathedral, containsCrypt, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsCrypt Context triple: [Urbino Cathedral, containsCrypt, yes]
-
A.
hasCrypt
chosen
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.
cryptographicType
Indicates the specific kind or category of cryptographic method, algorithm, or primitive associated with an entity or operation.
-
D.
dataIsEncrypted
Indicates that the referenced data is stored or transmitted in an encrypted form rather than in plaintext.
-
E.
cryptographicRelevance
Indicates that something has significance, impact, or utility within a cryptographic context, such as for security, encryption, or cryptographic analysis.
- 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_69e248ffc0888190ae23c4731eb8b7ac |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b35a513c8190a251fe2f55b23d7c |
completed | April 29, 2026, 7:29 a.m. |
| PD | Predicate disambiguation | batch_69f118d7903c8190bb590a71771e93af |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:49 p.m.