Triple
T17234227
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chrome Beta channel |
E418318
|
entity |
| Predicate | testingAudience |
P92295
|
FINISHED |
| Object | early adopters |
—
|
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: early adopters | Statement: [Chrome Beta channel, testingAudience, early adopters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: testingAudience Context triple: [Chrome Beta channel, testingAudience, early adopters]
-
A.
reportAudience
Indicates the intended recipients or target audience for a given report.
-
B.
hasAudienceReach
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.
-
C.
intendedAudienceInteraction
chosen
Indicates that one entity is the target group or audience with whom another entity is meant to interact or engage.
-
D.
testedTribe
Indicates that an entity (such as a person or group) has conducted a test or examination on a particular tribe.
-
E.
audienceComposition
Indicates the makeup or distribution of different groups or segments within an audience in relation to 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_69d886d8e96081909870bff6c3d0bf09 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42dfa0a408190880804d463305867 |
completed | April 19, 2026, 1:20 a.m. |
| PD | Predicate disambiguation | batch_69e3832553ac819091aa917c84f755b6 |
completed | April 18, 2026, 1:12 p.m. |
Created at: April 10, 2026, 5:39 a.m.