Triple
T22770011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | University College School, London |
E563527
|
entity |
| Predicate | hasPreparatorySite |
P62923
|
FINISHED |
| Object | Hampstead junior school site |
—
|
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: Hampstead junior school site | Statement: [University College School, London, hasPreparatorySite, Hampstead junior school site]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPreparatorySite Context triple: [University College School, London, hasPreparatorySite, Hampstead junior school site]
-
A.
hasPreparationContext
Indicates that an entity is associated with a specific situational or environmental context in which its preparation or setup occurs.
-
B.
isPreparedAs
Indicates that one entity is made ready, arranged, or configured in a particular way or form as specified by another entity.
-
C.
preparedAt
Indicates the time or place at which something was prepared or made ready.
-
D.
preparesFor
Indicates that one entity is used, designed, or undertaken in order to get another entity ready for a future event, state, or activity.
-
E.
hasSiteUse
chosen
Indicates that a site is used or designated for a particular function, activity, or purpose.
- 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_69e24554497c819080b996e071de27c2 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17b5cea44819097290351da9c488d |
completed | April 29, 2026, 3:30 a.m. |
| PD | Predicate disambiguation | batch_69eed2b88d88819096015deb6a648801 |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:27 p.m.