Triple
T14894633
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rotherwick |
E359838
|
entity |
| Predicate | nearestTown |
P350
|
FINISHED |
| Object | Hook |
E74486
|
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: Hook | Statement: [Rotherwick, nearestTown, Hook]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hook Context triple: [Rotherwick, nearestTown, Hook]
-
A.
Hook
"Hook" is a 1991 fantasy adventure film directed by Steven Spielberg that reimagines an adult Peter Pan returning to Neverland to rescue his children from Captain Hook.
-
B.
Hook
Hook is a suburban area within the Royal Borough of Kingston upon Thames in southwest London, England.
-
C.
Hook
Hook is a surname most notably associated with Theodore Hook, a 19th-century English writer and notorious practical joker.
-
D.
Hook
Hook is the NATO reporting name for the Mil Mi-6, a large Soviet-era heavy transport helicopter widely used for military and civilian roles.
-
E.
Hook
chosen
Hook is a village in Hampshire, England, known as a commuter settlement with good transport links to nearby towns and London.
- 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_69d827980cbc8190a0c569ae3940a1d9 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69ded5f9d10c819091732d7a5a42a682 |
completed | April 15, 2026, 12:04 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fe72b11584819084f32516cb0023a1 |
completed | May 8, 2026, 11:33 p.m. |
Created at: April 10, 2026, 2:10 a.m.