Triple
T28698973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cool Change |
E729495
|
entity |
| Predicate | marksFirstOnScreenAppearanceOf |
P29367
|
FINISHED |
| Object | Sara Sidle |
—
|
NE NERFINISHED |
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: Sara Sidle | Statement: [Cool Change, marksFirstOnScreenAppearanceOf, Sara Sidle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marksFirstOnScreenAppearanceOf Context triple: [Cool Change, marksFirstOnScreenAppearanceOf, Sara Sidle]
-
A.
firstOnPageAppearance
Indicates the position where an entity appears for the first time on a given page.
-
B.
firstAppearsAs
Indicates that an entity is introduced or shown in a particular form, role, or identity for the first time in a given context.
-
C.
firstAppearsAtLocation
Indicates the initial location where an entity is first observed, introduced, or comes into existence within a given context or sequence.
-
D.
firstAppearanceFor
chosen
Indicates that an entity marks the initial occurrence or debut of another entity within a given context or medium.
-
E.
isOftenFirstPointSeenBy
Indicates that one entity is typically the initial point of contact or the first thing encountered by another entity.
- 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_69f043e6e9688190b6bdd6e5665498ff |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f658ee40088190b71e1219407690d0 |
completed | May 2, 2026, 8:05 p.m. |
| PD | Predicate disambiguation | batch_69f65760fd3081908ffe014a5e2bf069 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 5:41 a.m.