Triple
T19932655
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roffey |
E479092
|
entity |
| Predicate | isLocatedNorthEastOf |
P15148
|
FINISHED |
| Object | Horsham town centre |
—
|
LITERAL 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: Horsham town centre | Statement: [Roffey, isLocatedNorthEastOf, Horsham town centre]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLocatedNorthEastOf Context triple: [Roffey, isLocatedNorthEastOf, Horsham town centre]
-
A.
locatedNorthEastOf
chosen
Indicates that one entity is positioned to the north-east of another entity in space.
-
B.
locatedEastOf
Indicates that one entity is positioned geographically to the east of another entity.
-
C.
liesNorthwestOf
Indicates that one entity is located to the northwest of another entity, combining both a more northern and more western position relative to it.
-
D.
liesSoutheastOf
Indicates that one entity is located to the southeast of another, combining both a southern and eastern directional relationship.
-
E.
locatedSouthWestOf
Indicates that one entity is positioned to the southwest of another entity, combining both a southern and western relative location.
- F. None of above.
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_69d8e521855c8190b41871700afc8d6a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65a14a2348190b41f8e320fe661d6 |
completed | April 20, 2026, 4:53 p.m. |
| PD | Predicate disambiguation | batch_69e537f070b481908958e0e5911dcdc1 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:53 p.m.