Triple
T8513259
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Dark Tower IV: Wizard and Glass |
E201508
|
entity |
| Predicate | mainCharacter |
P1183
|
FINISHED |
| Object | Oy |
E192783
|
NE 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: Oy | Statement: [The Dark Tower IV: Wizard and Glass, mainCharacter, Oy]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Oy Context triple: [The Dark Tower IV: Wizard and Glass, mainCharacter, Oy]
-
A.
Oy
chosen
Oy is a loyal, intelligent billy-bumbler companion to Roland Deschain’s ka-tet in Stephen King’s The Dark Tower series.
-
B.
OY
OY is the official vehicle registration code assigned to Oyo State in southwestern Nigeria.
-
C.
OBY
OBY is the National Rail station code for Oyster Bay railway station.
-
D.
Oyilattam
Oyilattam is a traditional folk dance of Tamil Nadu, India, characterized by rhythmic group movements and vibrant steps often performed during festivals and rural celebrations.
-
E.
The Yo
The Yo is a colloquial nickname for Youngstown, Ohio, often used by locals to refer to the city in a familiar, informal way.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ca8320e5748190ac2c585a0bba8193 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe60cdfcc819081a9be1229378ba0 |
completed | March 31, 2026, 3:19 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ce4e4e64f481908ddf99570fe59332 |
completed | April 2, 2026, 11:09 a.m. |
Created at: March 30, 2026, 6:15 p.m.