Triple
T16303079
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zoom-Zoom |
E395837
|
entity |
| Predicate | perceivedAudience |
P10804
|
FINISHED |
| Object | drivers who enjoy spirited driving |
—
|
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: drivers who enjoy spirited driving | Statement: [Zoom-Zoom, perceivedAudience, drivers who enjoy spirited driving]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: perceivedAudience Context triple: [Zoom-Zoom, perceivedAudience, drivers who enjoy spirited driving]
-
A.
relatesToAudience
Indicates a general relationship or relevance between something and a particular audience or group of recipients.
-
B.
typicalAudience
chosen
Indicates the group of people for whom something (such as a work, product, or resource) is primarily intended or most suitable.
-
C.
audienceOrientation
Indicates how something is directed, tailored, or positioned with respect to a particular audience or group of recipients.
-
D.
audienceComposition
Indicates the makeup or distribution of different groups or segments within an audience in relation to something.
-
E.
audienceScale
Indicates the relative size or reach of the audience associated with an entity, event, or communication.
- 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_69d87f23bb088190a16fbb91a1957ea5 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e25e35157481909e5604b7dae7a2a2 |
completed | April 17, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69e219fa5508819097e9d383348bf174 |
completed | April 17, 2026, 11:31 a.m. |
Created at: April 10, 2026, 5:06 a.m.