Triple
T28218348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Velká pardubická steeplechase |
E711379
|
entity |
| Predicate | typicalAudienceScope |
P10804
|
FINISHED |
| Object | international |
—
|
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: international | Statement: [Velká pardubická steeplechase, typicalAudienceScope, international]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalAudienceScope Context triple: [Velká pardubická steeplechase, typicalAudienceScope, international]
-
A.
typicalAudience
chosen
Indicates the group of people for whom something (such as a work, product, or resource) is primarily intended or most suitable.
-
B.
typicalScope
Indicates the usual or expected range, extent, or domain within which something normally applies, operates, or is relevant.
-
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.
targetAudienceKnowledge
Indicates the level or type of prior knowledge that the intended audience is expected to have.
- 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_69efb51cb5288190818c1f63a266af11 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_6a00781b749c8190921c46e110cae0b0 |
completed | May 10, 2026, 12:20 p.m. |
| PD | Predicate disambiguation | batch_6a0077df3c8481909fabc9e84f5936e3 |
completed | May 10, 2026, 12:19 p.m. |
Created at: April 27, 2026, 10:44 p.m.