Triple
T30466030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Other Band Tour |
E775142
|
entity |
| Predicate | hasTouringFormat |
P148401
|
FINISHED |
| Object | arena concerts |
—
|
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: arena concerts | Statement: [Other Band Tour, hasTouringFormat, arena concerts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTouringFormat Context triple: [Other Band Tour, hasTouringFormat, arena concerts]
-
A.
hasPlayFormat
Indicates that something (such as a game, media, or activity) is associated with a particular format or mode in which it is played or experienced.
-
B.
hasTouringConfiguration
chosen
Indicates that an entity is associated with a specific setup or arrangement used for touring activities.
-
C.
hasFormFactor
Indicates that one entity possesses or is characterized by a particular physical or structural form factor defined by another entity.
-
D.
hasTourVersion
Indicates that one entity is a specific tour-related version or variant of another entity.
-
E.
usesFilmFormat
Indicates that one entity employs or is recorded in a particular film format associated with the other 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_69f2249622a48190b1fae2e3e4ee958a |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f791cc969c8190bf187d6031a030d5 |
completed | May 3, 2026, 6:19 p.m. |
| PD | Predicate disambiguation | batch_69f791033d288190b118029fe412b9c9 |
completed | May 3, 2026, 6:16 p.m. |
Created at: April 29, 2026, 8:11 p.m.