Triple

T16246017
Position Surface form Disambiguated ID Type / Status
Subject Jellicoe Wharf E394372 entity
Predicate namedAfter P63 FINISHED
Object Jellicoe E5284 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: Jellicoe | Statement: [Jellicoe Wharf, namedAfter, Jellicoe]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Jellicoe
Context triple: [Jellicoe Wharf, namedAfter, Jellicoe]
  • A. Jellicoe
    Jellicoe is a small rural community within the Township of Greenstone in northern Ontario, Canada.
  • B. Lord Jellicoe chosen
    Lord Jellicoe was a British Royal Navy admiral best known for commanding the Grand Fleet at the Battle of Jutland during World War I and later serving in senior naval and imperial administrative roles.
  • C. Pellew
    Pellew is a surname most notably associated with Edward Pellew, a distinguished British Royal Navy officer of the late 18th and early 19th centuries.
  • D. Admiral Alexander Hood
    Admiral Alexander Hood was a prominent late 18th-century British naval officer and peer, noted for his leadership in major fleet actions against Revolutionary France.
  • E. Admiral Grant
    Admiral Grant is a fictional high-ranking naval officer portrayed by actor John Amos.
  • 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_69d87f2171208190951025e526947816 completed April 10, 2026, 4:40 a.m.
NER Named-entity recognition batch_69e24561d250819096f709ea8751fcb9 completed April 17, 2026, 2:36 p.m.
NED1 Entity disambiguation (via context triple) batch_6a000ee135b881909cc1b6919bc7af29 completed May 10, 2026, 4:51 a.m.
Created at: April 10, 2026, 5:04 a.m.