Triple
T19317484
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ormond Hotel episode in Ulysses |
E483135
|
entity |
| Predicate | locationWithinBook |
P66157
|
FINISHED |
| Object | middle episodes of Ulysses |
—
|
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: middle episodes of Ulysses | Statement: [Ormond Hotel episode in Ulysses, locationWithinBook, middle episodes of Ulysses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationWithinBook Context triple: [Ormond Hotel episode in Ulysses, locationWithinBook, middle episodes of Ulysses]
-
A.
locationWithinFiction
Indicates that one fictional location is situated inside or contained within another fictional location.
-
B.
partOfBook
Indicates that one entity is a component or section contained within a larger book entity.
-
C.
hasPositionInBook
chosen
Indicates that an entity occupies a specific position or location within a book.
-
D.
readingLocation
Indicates the place or position where a reading activity occurs or is associated with an entity.
-
E.
locationInDocument
Indicates that one entity specifies where another entity is situated or referenced within a document.
- 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.