Triple
T15841126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Main Market |
E384102
|
entity |
| Predicate | listingVenueFor |
P25526
|
FINISHED |
| Object | Swedish blue-chip companies |
—
|
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: Swedish blue-chip companies | Statement: [Main Market, listingVenueFor, Swedish blue-chip companies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: listingVenueFor Context triple: [Main Market, listingVenueFor, Swedish blue-chip companies]
-
A.
homeMeetsVenue
Indicates that a home team plays its scheduled match at a specified venue.
-
B.
typicalVenues
chosen
Indicates that the specified locations are common or standard places where the associated activity, event, or entity usually occurs or is hosted.
-
C.
featuresVenue
Indicates that one entity includes, hosts, or is associated with a particular venue as part of its offering or context.
-
D.
usesVenues
Indicates that one entity makes use of or operates within specific venues or locations to carry out its activities or services.
-
E.
homeVenueAlsoUsedBy
Indicates that the venue serving as a home location for one entity is also used as a venue by another entity.
- 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_69d86da34c888190976e06c4019d415a |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e142e764088190afba6c5c1acf8199 |
completed | April 16, 2026, 8:13 p.m. |
| PD | Predicate disambiguation | batch_69e005418f588190824d91ff7974dada |
completed | April 15, 2026, 9:38 p.m. |
Created at: April 10, 2026, 4:50 a.m.