Triple
T14239474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Horror of Fang Rock |
E352968
|
entity |
| Predicate | featuresCharacter |
P626
|
FINISHED |
| Object | Leela |
E352363
|
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: Leela | Statement: [Horror of Fang Rock, featuresCharacter, Leela]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Leela Context triple: [Horror of Fang Rock, featuresCharacter, Leela]
-
A.
Leela
chosen
Leela is a companion of the Fourth Doctor in the classic British science fiction television series Doctor Who.
-
B.
Leela
Leela is the one-eyed, tough yet compassionate spaceship captain from the animated television series "Futurama."
-
C.
Seeta
Seeta is a rapidly growing suburban town and trading center in central Uganda, located along the Kampala–Jinja highway near Mukono.
-
D.
Neela
Neela is a central street racer and love interest in the film "The Fast and the Furious: Tokyo Drift," known for her drifting skills in Tokyo's underground racing scene.
-
E.
Neela
Neela is a prominent commander in the monkey kingdom of Kishkindha in the Indian epic Ramayana, known for his leadership in Rama’s campaign against Ravana.
- 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_69d8278adc7c8190a9218d69bce3c4e6 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de62432fb48190b153805b85c4f2d2 |
completed | April 14, 2026, 3:50 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd3d1081148190b8830615a34711c0 |
completed | May 8, 2026, 1:32 a.m. |
Created at: April 10, 2026, 1:08 a.m.