Triple
T13564779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peppermint Patty |
E324005
|
entity |
| Predicate | schoolPerformance |
P94190
|
FINISHED |
| Object | poor |
—
|
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: poor | Statement: [Peppermint Patty, schoolPerformance, poor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: schoolPerformance Context triple: [Peppermint Patty, schoolPerformance, poor]
-
A.
academicPerformance
chosen
Indicates the level or quality of achievement an entity demonstrates in academic or educational activities.
-
B.
schoolBoard
Indicates that an entity serves as or is governed by a school board responsible for overseeing educational policies and administration.
-
C.
schoolDistrictReputation
Indicates the perceived quality and standing of a school district based on factors like academics, safety, resources, and community opinion.
-
D.
studentsPerformAt
Indicates that students carry out or present a performance, activity, or task at a particular event, venue, or context.
-
E.
schoolBoardSystem
Indicates a governance or administrative relationship in which a school board oversees, manages, or makes decisions for a school system or district.
- 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_69d8076830b48190910a902bae5888e2 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbb00cecd48190a9a2caff3d424817 |
completed | April 12, 2026, 2:45 p.m. |
| PD | Predicate disambiguation | batch_69dbae161a0481909f9d3f40ca4e0ac5 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:47 p.m.