Triple
T12913199
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | the Enchiridion |
E308909
|
entity |
| Predicate | coverSymbol |
P106977
|
FINISHED |
| Object | skull-like horned face |
—
|
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: skull-like horned face | Statement: [the Enchiridion, coverSymbol, skull-like horned face]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coverSymbol Context triple: [the Enchiridion, coverSymbol, skull-like horned face]
-
A.
cover
Indicates that one entity extends over, conceals, protects, or provides a surface or layer for another entity.
-
B.
coverText
Indicates that one text serves as the cover or front-facing textual representation for another work or resource.
-
C.
coverVersionBy
Indicates that one creative work is a cover version performed or produced by a particular artist or entity.
-
D.
coverLocation
Indicates that one entity serves as a covering or protective layer positioned at or over a specific location of another entity.
-
E.
coverUpBy
Indicates that one entity conceals, suppresses, or hides the actions, information, or wrongdoing associated with another entity.
- F. None of above. chosen
Provenance (4 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_69d7bdf92b588190acdf2a2291ac4590 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9719f96248190b746f9d4a468560c |
completed | April 10, 2026, 9:54 p.m. |
| PD | Predicate disambiguation | batch_69d96fa9b7708190a9e9fa30f59ff580 |
completed | April 10, 2026, 9:46 p.m. |
| PDg | Predicate description generation | batch_69d9708a86bc8190bcdcf97e845bb413 |
completed | April 10, 2026, 9:50 p.m. |
Created at: April 9, 2026, 5:41 p.m.