Triple
T29173310
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thornton Primary School |
E739530
|
entity |
| Predicate | locatedInLocalArea |
P40
|
FINISHED |
| Object | Thornton |
—
|
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: Thornton | Statement: [Thornton Primary School, locatedInLocalArea, Thornton]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInLocalArea Context triple: [Thornton Primary School, locatedInLocalArea, Thornton]
-
A.
localityOf
Indicates that one entity is the specific place, area, or locality in which another entity is situated or occurs.
-
B.
likelyLocatedIn
Indicates that an entity is probably situated within or associated with a particular location, though not with absolute certainty.
-
C.
locatedInOrAdjacentTo
Indicates that one entity is either situated within the boundaries of another entity or directly next to it, sharing a common border or edge.
-
D.
residesNear
Indicates that one entity lives or is located in close physical proximity to another entity.
-
E.
locatedIn
chosen
Indicates that one entity exists or is situated within the spatial, administrative, or conceptual boundaries of another entity.
- 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_69f07cb6394c8190ab7842c48e699e2a |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_6a0008225cc081909ff1fd0639859dc4 |
completed | May 10, 2026, 4:22 a.m. |
| PD | Predicate disambiguation | batch_6a0007bac5d8819098aff8031d4abe5d |
completed | May 10, 2026, 4:21 a.m. |
Created at: April 28, 2026, 11:53 a.m.