Triple
T19317483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ormond Hotel episode in Ulysses |
E483135
|
entity |
| Predicate | JoyceSchemaTechnique |
P51617
|
FINISHED |
| Object | fuga per canonem |
—
|
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: fuga per canonem | Statement: [Ormond Hotel episode in Ulysses, JoyceSchemaTechnique, fuga per canonem]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: JoyceSchemaTechnique Context triple: [Ormond Hotel episode in Ulysses, JoyceSchemaTechnique, fuga per canonem]
-
A.
hasDramaticTechnique
Indicates that one entity employs, features, or is characterized by a particular dramatic technique associated with another entity.
-
B.
featuresTechnique
chosen
Indicates that something incorporates or makes use of a particular technique as part of its content or execution.
-
C.
spellingTechnique
Indicates a method or strategy used to spell words correctly.
-
D.
designMethod
Indicates that one entity is used as the method, approach, or technique by which another entity is designed or created.
-
E.
inscriptionTechnique
Indicates the method or process used to create an inscription on a surface.
- 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_69d8e8d13e3c81909d91d1d5ec37c095 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e60d85046c81909d972a6b369b0c2b |
completed | April 20, 2026, 11:27 a.m. |
| PD | Predicate disambiguation | batch_69e4dd0ef66881909d489d634eee817a |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:32 p.m.