Triple
T17327878
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plumfield Estate School |
E420733
|
entity |
| Predicate | notablePupilType |
P94682
|
FINISHED |
| Object | former misfit boys |
—
|
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: former misfit boys | Statement: [Plumfield Estate School, notablePupilType, former misfit boys]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notablePupilType Context triple: [Plumfield Estate School, notablePupilType, former misfit boys]
-
A.
notablePupil
Indicates that one person is a distinguished or noteworthy student or protégé of another person.
-
B.
notableStudent
Indicates that a person is a distinguished or particularly significant student of another individual or institution.
-
C.
notableStudentOrCircle
Indicates that there exists a notable student or intellectual circle associated with a given person or entity.
-
D.
notableStudentTransmitter
Indicates that one entity is recognized as a notable or distinguished student who has been taught, mentored, or influenced by another entity.
-
E.
notableTypeOf
chosen
Indicates that one entity is a particularly prominent, well-known, or exemplary instance or subtype 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_69d889d3adc881909319f1edb8d2a956 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e439d42154819093a240f677a63145 |
completed | April 19, 2026, 2:11 a.m. |
| PD | Predicate disambiguation | batch_69e3b021a5bc81909ae55406f9d0b37f |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:43 a.m.