Triple
T22588254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blackthorn |
E564860
|
entity |
| Predicate | title |
P38
|
FINISHED |
| Object | Blackthorn |
—
|
NE NERFINISHED |
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: Blackthorn | Statement: [Blackthorn, title, Blackthorn]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Blackthorn Context triple: [Blackthorn, title, Blackthorn]
-
A.
Blackthorn
chosen
Blackthorn is a 2011 Western film that imagines an aging Butch Cassidy living in Bolivia years after his presumed death.
-
B.
Blackthorn
Blackthorn is a residential area and housing estate on the eastern side of Northampton, England.
-
C.
Glapthorn
Glapthorn is a small rural village in Northamptonshire, England, known for its traditional countryside setting and proximity to the market town of Oundle.
-
D.
Thorn
Thorn is a significant city in the Black Marsh province of The Elder Scrolls universe, known as an Argonian settlement with regional importance.
-
E.
Thorn
Thorn is a surname most notably associated with Rod Thorn, a prominent figure in American professional basketball as both a player and executive.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e245836014819091b91ed3074742a3 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f1615ea5bc8190b7760cd0de9669dd |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 2:47 p.m.