Triple
T8969116
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Simone Smith |
E214216
|
entity |
| Predicate | mediaAppearanceAs |
P24836
|
FINISHED |
| Object | herself |
—
|
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: herself | Statement: [Simone Smith, mediaAppearanceAs, herself]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mediaAppearanceAs Context triple: [Simone Smith, mediaAppearanceAs, herself]
-
A.
mediaAppearanceType
Indicates the specific kind or category of media appearance associated with an entity (e.g., interview, feature, cameo, or performance).
-
B.
mediaProfile
Indicates a relationship where a media-related profile or account is associated with an entity, typically representing its presence or identity in media contexts.
-
C.
hasMediaAppearanceIn
Indicates that an entity appears or is featured as media content within a specified media work, program, or publication.
-
D.
appearsAs
chosen
Indicates that one entity is presented, perceived, or manifested in the form, role, or guise of another entity.
-
E.
mediaDependentInterface
Indicates that one interface or interaction is contingent on, or varies according to, the characteristics or type of the media involved.
- 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_69ca839dbf608190a2f5990477115d29 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6765babc8190a4a3b79aa21047c8 |
completed | April 1, 2026, 12:31 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed9a2d48190ad11381078e823b7 |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:01 p.m.