Triple
T17270107
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gateacre |
E419232
|
entity |
| Predicate | hasNeighbourhood |
P4813
|
FINISHED |
| Object | Hunts Cross |
E419233
|
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: Hunts Cross | Statement: [Gateacre, hasNeighbourhood, Hunts Cross]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hunts Cross Context triple: [Gateacre, hasNeighbourhood, Hunts Cross]
-
A.
Hunts Cross
chosen
Hunts Cross is a suburban residential area in south Liverpool, England, known for its railway station and proximity to Liverpool John Lennon Airport.
-
B.
Brent Cross
Brent Cross is a district in northwest London best known for its large shopping centre and major road junction.
-
C.
Turners Cross
Turners Cross is a residential suburb of Cork City, Ireland, known for its football stadium and local community amenities.
-
D.
Leyland Cross
Leyland Cross is a historic stone market cross and local landmark located in the town of Leyland, Lancashire, England.
-
E.
Tricketts Cross
Tricketts Cross is a residential suburb of the town of Ferndown in Dorset, 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_69d886da626481908a14ce7830329a35 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42f4917ec819096356ad2ed24d51d |
completed | April 19, 2026, 1:26 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a01794a09b8819086da30f38c6d4c20 |
completed | May 11, 2026, 6:38 a.m. |
Created at: April 10, 2026, 5:40 a.m.