Triple
T1022626
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NWR |
E22071
|
entity |
| Predicate | serviceAudience |
P19115
|
FINISHED |
| Object | general public |
—
|
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: general public | Statement: [NWR, serviceAudience, general public]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceAudience Context triple: [NWR, serviceAudience, general public]
-
A.
typicalAudience
Indicates the group of people for whom something (such as a work, product, or resource) is primarily intended or most suitable.
-
B.
categoryOfPeopleServed
chosen
Indicates the type or group of people that are the primary recipients or beneficiaries of a service or activity.
-
C.
secondaryAudience
Indicates that an entity is a secondary or additional intended audience or target group for another entity (such as a work, message, or product), beyond the primary audience.
-
D.
hasAudience
Indicates that an entity is intended to be received, viewed, or engaged with by a particular group of people.
-
E.
servesUsers
Indicates that an entity provides services, functionality, or benefits to one or more users.
- 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_69a493d6e380819097b384986ffc315c |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b7e0f8908190bfe0a4cd8b31dfed |
completed | March 1, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69a4b72619cc8190932fdfa0c74dc055 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:41 p.m.