Triple
T20789879
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reigate Priory Junior School |
E511743
|
entity |
| Predicate | hasHistoricPremises |
P141548
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Reigate Priory Junior School, hasHistoricPremises, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricPremises Context triple: [Reigate Priory Junior School, hasHistoricPremises, true]
-
A.
hasHistoricHut
Indicates that an entity possesses, contains, or is associated with a historic hut.
-
B.
hasNearbyHistoricalEstate
Indicates that one entity is located close to another entity that is a recognized historical estate.
-
C.
hasHistoricGround
Indicates that one entity is located on, associated with, or includes land or grounds of historical significance related to another entity.
-
D.
hasFormerBuilding
Indicates that an entity previously occupied or used a different building, which is identified as its former building.
-
E.
containsHistoricHouse
Indicates that one entity includes or encompasses a historic house within its boundaries or composition.
- F. None of above. chosen
Provenance (4 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_69e0b4cb83948190bd57bec21d78ed53 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c28f0e1081909f18dddfc6ec084c |
completed | April 21, 2026, 12:19 a.m. |
| PD | Predicate disambiguation | batch_69e5c0575b1c81908d010223fcd1213e |
completed | April 20, 2026, 5:57 a.m. |
| PDg | Predicate description generation | batch_69e5c3cbe5788190b7ace43bfdac2ef6 |
completed | April 20, 2026, 6:12 a.m. |
Created at: April 16, 2026, 12:38 p.m.