Triple
T28650668
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Blue Closet |
E725184
|
entity |
| Predicate | hasMedievalImagery |
P66656
|
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: [The Blue Closet, hasMedievalImagery, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMedievalImagery Context triple: [The Blue Closet, hasMedievalImagery, yes]
-
A.
hasMedievalElements
chosen
Indicates that something incorporates characteristics, motifs, or features typical of the medieval period.
-
B.
isMedieval
Indicates that something belongs to, originates from, or is characteristic of the medieval (Middle Ages) period.
-
C.
hasMedievalBuilding
Indicates that one entity possesses, contains, or includes a building dating from the medieval period.
-
D.
isMedievalForm
Indicates that one form or variant of something is specifically the medieval version of another form or of a general concept.
-
E.
medievalAssociation
Indicates a relationship or involvement between entities specifically within a medieval context, such as shared roles, activities, or affiliations characteristic of the Middle Ages.
- 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_69f01d8423888190bd2f4e52605bf261 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69fcdf2394748190b35cead3e208447d |
completed | May 7, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe344ec8190a0471911952f4b82 |
completed | May 7, 2026, 6:37 p.m. |
Created at: April 28, 2026, 4:51 a.m.