Triple
T32284787
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Robb White |
E824794
|
entity |
| Predicate | wrotePrimarilyForAudience |
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: [Robb White, wrotePrimarilyForAudience, young adults]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wrotePrimarilyForAudience Context triple: [Robb White, wrotePrimarilyForAudience, young adults]
-
A.
writesForAudience
chosen
Indicates that an agent creates written content intended specifically for a particular audience or readership.
-
B.
primarilyFor
Indicates that something is mainly intended, designed, or used for a particular purpose, function, or beneficiary, even if it may have secondary uses.
-
C.
originallyWrittenFor
Indicates that a work was initially created or composed with a particular recipient, medium, context, or purpose in mind.
-
D.
typicalAudience
Indicates the group of people for whom something (such as a work, product, or resource) is primarily intended or most suitable.
-
E.
relatesToAudience
Indicates a general relationship or relevance between something and a particular audience or group of recipients.
- 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_69f3490f404081908450db66884f4334 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c1bb5f248190834161b5a6ba1ece |
completed | May 3, 2026, 3:32 a.m. |
| PD | Predicate disambiguation | batch_69f6bd25bed08190befcabd3a41ffadf |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 12:43 a.m.