Triple
T8579851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pearl Bailey High School |
E203141
|
entity |
| Predicate | notableStaffInFiction |
P61558
|
FINISHED |
| Object | Principal Lewis |
—
|
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: Principal Lewis | Statement: [Pearl Bailey High School, notableStaffInFiction, Principal Lewis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableStaffInFiction Context triple: [Pearl Bailey High School, notableStaffInFiction, Principal Lewis]
-
A.
notableWorkCharacter
Indicates that a character appears in, is associated with, or plays a role in a particular notable work.
-
B.
notablePersonnel
Indicates that the subject has associated individuals who are particularly important, distinguished, or prominent in relation to it.
-
C.
notableCharacterType
Indicates that an entity is a notable or prominent example of a specified character type or role.
-
D.
hasFictionalStaffMember
chosen
Indicates that an entity includes or employs a staff member who is a fictional character.
-
E.
notableCharacterGroup
Indicates that a group of characters is especially prominent, significant, or noteworthy within a given context or work.
- 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_69ca8328ebe481909a8c038fa79959b4 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbea9a0708819084cb8b8d84017864 |
completed | March 31, 2026, 3:39 p.m. |
| PD | Predicate disambiguation | batch_69cbd11b13108190b07f8f161425a585 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:22 p.m.