Triple
T33153722
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mildred Ames |
E848508
|
entity |
| Predicate | writingAudience |
P54225
|
FINISHED |
| Object | young adults |
—
|
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: young adults | Statement: [Mildred Ames, writingAudience, young adults]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: writingAudience Context triple: [Mildred Ames, writingAudience, young adults]
-
A.
writesForAudience
chosen
Indicates that an agent creates written content intended specifically for a particular audience or readership.
-
B.
relatesToAudience
Indicates a general relationship or relevance between something and a particular audience or group of recipients.
-
C.
targetAudienceWithinFiction
Indicates that the intended audience of a work exists as characters or entities within the fictional world depicted by that work.
-
D.
typicalAudience
Indicates the group of people for whom something (such as a work, product, or resource) is primarily intended or most suitable.
-
E.
readership
Indicates the relationship in which one party reads, follows, or is the audience for the written or published work of another.
- 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_69f3495b02d08190bb3d366823dffc21 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6db6af1d88190989810182354d60f |
completed | May 3, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69f6d82d068c8190940a3200ed760e38 |
completed | May 3, 2026, 5:07 a.m. |
Created at: May 1, 2026, 1:28 a.m.