Triple
T28678927
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wadesmill |
E725953
|
entity |
| Predicate | formerlyOn |
P55436
|
FINISHED |
| Object | Great North Road |
—
|
NE NERFINISHED |
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: Great North Road | Statement: [Wadesmill, formerlyOn, Great North Road]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerlyOn Context triple: [Wadesmill, formerlyOn, Great North Road]
-
A.
formerlyLocatedOn
chosen
Indicates that an entity was once located on or situated upon another entity, but is no longer in that position.
-
B.
formerlyConsidered
Indicates that something was previously regarded or classified in a certain way, but that evaluation or status has since changed.
-
C.
formerlyConfiguration
Indicates that one entity was previously configured or arranged in the state or setup represented by the other entity, but is no longer so.
-
D.
formerName
Indicates that an entity was previously known by a different name in the past.
-
E.
usedToBe
Indicates that something held a particular state, role, or property in the past but no longer does in the present.
- 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_69f01d867608819086bc3e6b4f9de866 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69fdf5d05cc481909ec9e1b1f0784279 |
completed | May 8, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69fdf0cdd6948190838864ab3120dfa6 |
completed | May 8, 2026, 2:18 p.m. |
Created at: April 28, 2026, 5:08 a.m.