Triple
T32020582
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brighton College |
E817675
|
entity |
| Predicate | acceptsBoardersFrom |
P166354
|
FINISHED |
| Object | United Kingdom |
—
|
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: United Kingdom | Statement: [Brighton College, acceptsBoardersFrom, United Kingdom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: acceptsBoardersFrom Context triple: [Brighton College, acceptsBoardersFrom, United Kingdom]
-
A.
admitsBoarders
chosen
Indicates that an entity accepts or allows boarders (people who live and/or take meals there) to reside on its premises.
-
B.
haveOpenBordersThrough
Indicates that one entity allows unrestricted or minimally restricted cross-border movement or access via another specified entity or route.
-
C.
restrictedImmigrantsFrom
Indicates that one entity imposed limitations or prohibitions on immigrants originating from another entity.
-
D.
hasBorderControlBy
Indicates that the border of one entity is monitored, regulated, or managed by another entity.
-
E.
hasBorderControlFacility
Indicates that one location possesses an official facility responsible for managing and controlling border crossings to or from another 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_69f348fb04e4819081f4eab040ed7959 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b466aaa08190bcafc15b3b2d3d31 |
completed | May 3, 2026, 2:35 a.m. |
| PD | Predicate disambiguation | batch_69f6b151ad008190836c1bcdec503ce2 |
completed | May 3, 2026, 2:22 a.m. |
Created at: May 1, 2026, 12:16 a.m.