Triple
T36152918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coolsville High School |
E1045640
|
entity |
| Predicate | commonStoryElement |
P35676
|
FINISHED |
| Object | student life |
—
|
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: student life | Statement: [Coolsville High School, commonStoryElement, student life]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonStoryElement Context triple: [Coolsville High School, commonStoryElement, student life]
-
A.
storyElement
chosen
Indicates that one entity functions as a narrative component or part within the structure of another entity’s story.
-
B.
notableFeatureInStory
Indicates that a particular feature, element, or characteristic plays a significant or prominent role within a story.
-
C.
storyBy
Indicates that one entity is the creator or author of the story associated with another entity.
-
D.
storylineEvent
Indicates that one event occurs as a distinct step or component within a larger narrative or storyline.
-
E.
coreNarrative
Indicates the primary storyline or central sequence of events that forms the main thread of a narrative.
- 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_69f76e38903c8190a52887620f90aabe |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69feecf1bb248190ba30f0bb1d22ee08 |
completed | May 9, 2026, 8:14 a.m. |
| PD | Predicate disambiguation | batch_69feea5f27748190b223ee4e3ba5a678 |
completed | May 9, 2026, 8:03 a.m. |
Created at: May 3, 2026, 4:08 p.m.