Triple
T14543082
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HOTA Outdoor Stage |
E341217
|
entity |
| Predicate | typicalAudienceSetting |
P56401
|
FINISHED |
| Object | picnic-style lawn seating |
—
|
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: picnic-style lawn seating | Statement: [HOTA Outdoor Stage, typicalAudienceSetting, picnic-style lawn seating]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalAudienceSetting Context triple: [HOTA Outdoor Stage, typicalAudienceSetting, picnic-style lawn seating]
-
A.
typicalAudience
Indicates the group of people for whom something (such as a work, product, or resource) is primarily intended or most suitable.
-
B.
audienceSetting
chosen
Indicates the context or environment in which an audience is situated or addressed.
-
C.
relatesToAudience
Indicates a general relationship or relevance between something and a particular audience or group of recipients.
-
D.
typicalAudienceResponse
Indicates the usual or expected reaction, behavior, or feedback that an audience has in response to a given work, event, or communication.
-
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_69d822db9c8481908213ceb39585f792 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb1be5a8081909bf727e28a5bba4a |
completed | April 14, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69de5c546c7081909e27d504ec360c5c |
completed | April 14, 2026, 3:25 p.m. |
Created at: April 10, 2026, 1:22 a.m.