Triple
T33185972
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ashlie Walker |
E849468
|
entity |
| Predicate | media presence |
P21248
|
FINISHED |
| Object | limited |
—
|
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: limited | Statement: [Ashlie Walker, media presence, limited]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: media presence Context triple: [Ashlie Walker, media presence, limited]
-
A.
mediaPresence
chosen
Indicates the extent to which something is visible, represented, or covered within various media channels or platforms.
-
B.
socialMediaAppearance
Indicates that an entity is featured, mentioned, or otherwise present in a piece of content on a social media platform.
-
C.
mediaInfluence
Indicates that one entity affects, shapes, or alters another entity’s attitudes, behaviors, or perceptions through media content or channels.
-
D.
mediaSignificance
Indicates the degree of importance, impact, or prominence that something holds within media coverage or representation.
-
E.
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.
- 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_69f3495e0f108190a6a7006f79f9c2c3 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7516d5b4081908588a6feb541f355 |
completed | May 3, 2026, 1:45 p.m. |
| PD | Predicate disambiguation | batch_69f74d40ebb081909daf60623e38f41d |
completed | May 3, 2026, 1:27 p.m. |
Created at: May 1, 2026, 1:29 a.m.