Triple
T29306383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ariana Fletcher |
E743106
|
entity |
| Predicate | hasOnlineAudienceScope |
P82449
|
FINISHED |
| Object | international |
—
|
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: international | Statement: [Ariana Fletcher, hasOnlineAudienceScope, international]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOnlineAudienceScope Context triple: [Ariana Fletcher, hasOnlineAudienceScope, international]
-
A.
hasAudience
Indicates that an entity is intended to be received, viewed, or engaged with by a particular group of people.
-
B.
hasLiveAudienceCapability
Indicates that an entity is capable of supporting or engaging with a live, in-person audience.
-
C.
hasAudienceReach
chosen
Indicates the extent or scope of people or groups that are exposed to, can access, or are targeted by a particular entity, message, or activity.
-
D.
hasAudienceOrigin
Indicates that an audience is characterized by or associated with a particular geographic, cultural, or demographic origin.
-
E.
hasAudiencePolicy
Indicates that there is a specified rule or policy governing which audience or group is allowed to access, view, or receive something.
- 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_69f09123ed9881909f351f7541933f5e |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f969b4cc8190afb473a2d8b110bc |
completed | May 3, 2026, 7:29 a.m. |
Created at: April 28, 2026, 1:13 p.m.