Triple
T34429619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St Enda's School |
E883789
|
entity |
| Predicate | notableHeadmaster |
P28470
|
FINISHED |
| Object | Patrick Pearse |
E253328
|
NE 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: Patrick Pearse | Statement: [St Enda's School, notableHeadmaster, Patrick Pearse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableHeadmaster Context triple: [St Enda's School, notableHeadmaster, Patrick Pearse]
-
A.
hasNotableHeadmaster
chosen
Indicates that an institution or organization is associated with a headmaster who is particularly distinguished or noteworthy.
-
B.
successorAsHeadOfSlytherin
Indicates that one entity became the next head of Slytherin House after another entity.
-
C.
schoolHouseFounder
Indicates that an entity is the person who founded or established a particular school house.
-
D.
predecessorAsHeadOfGryffindor
Indicates that one entity previously served as the Head of Gryffindor House before another entity.
-
E.
notableProfessor
Indicates that a person holds or has held a professorship that is distinguished, prominent, or otherwise recognized as notable.
- F. None of above.
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_69f349c3dd2c819092cc9e64809f4a42 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a37bcf6f9d081908753c49b4dc3e19f |
completed | June 21, 2026, 10:29 a.m. |
| PD | Predicate disambiguation | batch_6a0379fbe4a08190bfe65ebd141164e9 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 2 a.m.