Triple
T33575538
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ABBA Voyage concert residency |
E860019
|
entity |
| Predicate | venueName |
P373
|
FINISHED |
| Object | ABBA Arena |
—
|
NE NERFINISHED |
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: ABBA Arena | Statement: [ABBA Voyage concert residency, venueName, ABBA Arena]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: venueName Context triple: [ABBA Voyage concert residency, venueName, ABBA Arena]
-
A.
venueAlsoKnownAs
Indicates that a venue has an alternative name or alias by which it is also known.
-
B.
venueNameAtTime
Indicates the name assigned to a particular venue during a specified time period.
-
C.
hasVenueName
Indicates that an entity has a specific name used to identify the venue where an event or activity takes place.
-
D.
venue
chosen
Indicates the place or location where an event, activity, or interaction takes place.
-
E.
venueAssociatedWith
Indicates that there is a relevant connection or linkage between an event, activity, or entity and a particular venue or location.
- 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_69f3497d37848190afcbb5ef3f5c7376 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6f74b95248190a3546b33dda2402d |
completed | May 3, 2026, 7:20 a.m. |
| PD | Predicate disambiguation | batch_69f6f6632dfc8190af85e258c8519207 |
completed | May 3, 2026, 7:16 a.m. |
Created at: May 1, 2026, 1:40 a.m.