Triple
T30864690
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Les Eurockéennes de Belfort |
E786163
|
entity |
| Predicate | typicalAudienceRegion |
P133613
|
FINISHED |
| Object | France |
E861
|
NE 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: France | Statement: [Les Eurockéennes de Belfort, typicalAudienceRegion, France]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalAudienceRegion Context triple: [Les Eurockéennes de Belfort, typicalAudienceRegion, France]
-
A.
viewershipRegion
Indicates the geographic region or area in which content is viewed or for which its audience is measured.
-
B.
hasTargetAudienceRegion
Indicates that something is intended for or directed toward an audience located in a specific geographic region.
-
C.
primaryRegionOfPopularity
Indicates the geographic region where something is most widely used, favored, or popular compared to other regions.
-
D.
countryAudience
chosen
Indicates that an audience is located in, associated with, or targeted within a specific country.
-
E.
typicalTargetRegion
Indicates the region or area that an action, process, or effect is most commonly directed toward or occurs in.
- F. None of above.
Provenance (4 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_69f224b9df2c819086f55f8bcf7f382e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a28c7c61868819095987b85b3913cc9 |
completed | June 10, 2026, 2:11 a.m. |
| PD | Predicate disambiguation | batch_6a0379e2fac0819089b522db3260028c |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 8:47 p.m.