Triple
T22354300
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Point Place High School |
E552610
|
entity |
| Predicate | hasFictionalStaff |
P61558
|
FINISHED |
| Object | teachers |
—
|
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: teachers | Statement: [Point Place High School, hasFictionalStaff, teachers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFictionalStaff Context triple: [Point Place High School, hasFictionalStaff, teachers]
-
A.
hasFictionalStaffMember
chosen
Indicates that an entity includes or employs a staff member who is a fictional character.
-
B.
hasFictionalMember
Indicates that a group, organization, or collection includes at least one member that is fictional rather than real.
-
C.
hasFictionalCoStar
Indicates that one entity appears as a co-star alongside another entity within a fictional work or narrative.
-
D.
hasFictionalSpokesperson
Indicates that an entity is represented or promoted by a spokesperson who is a fictional or imaginary character.
-
E.
hasFictionalPerformer
Indicates that an entity is associated with a performer who is a fictional or imaginary character rather than a real person.
- 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_69e11e4a0ad08190a385b4d343cf6524 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f157ceb2308190941f6507e605a612 |
completed | April 29, 2026, 12:58 a.m. |
| PD | Predicate disambiguation | batch_69e7300c20088190a59e5bf9e70384f3 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:44 p.m.