Triple

T7326023
Position Surface form Disambiguated ID Type / Status
Subject Brentwood E168876 entity
Predicate hasNearbySettlement P4647 FINISHED
Object Ingatestone E178826 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: Ingatestone | Statement: [Brentwood, hasNearbySettlement, Ingatestone]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ingatestone
Context triple: [Brentwood, hasNearbySettlement, Ingatestone]
  • A. Ingatestone chosen
    Ingatestone is a historic village and civil parish in southeast England known for its traditional architecture and commuter links to London.
  • B. Windlestone
    Windlestone is a village in County Durham, England, known for its historic country house, Windlestone Hall, and its rural surroundings.
  • C. Tilmanstone
    Tilmanstone is a small rural village in Kent, England, historically associated with coal mining and situated near the town of Dover.
  • D. Flotterstone
    Flotterstone is a popular walking and recreation area on the northern edge of the Pentland Hills near Edinburgh, known for its scenic reservoir, trails, and access to the surrounding hills.
  • E. Grindon
    Grindon is a residential suburb of Sunderland in the Wearside area of North East England.
  • 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_69c68a54cacc81908e3b773441f19566 completed March 27, 2026, 1:47 p.m.
NER Named-entity recognition batch_69c6f0a612c08190b7a3fefa811bbcec completed March 27, 2026, 9:03 p.m.
NED1 Entity disambiguation (via context triple) batch_69c7ef0e3e7481908e6cedbd3f0077ca completed March 28, 2026, 3:09 p.m.
Created at: March 27, 2026, 3:03 p.m.