Triple
T4092023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Žalgiris Arena |
E87724
|
entity |
| Predicate | hasSeatingCapacityForConcerts |
P2491
|
FINISHED |
| Object | up to 20000 |
—
|
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: up to 20000 | Statement: [Žalgiris Arena, hasSeatingCapacityForConcerts, up to 20000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSeatingCapacityForConcerts Context triple: [Žalgiris Arena, hasSeatingCapacityForConcerts, up to 20000]
-
A.
seatingCapacity
chosen
Indicates the maximum number of people that something (typically a venue or vehicle) is designed or allowed to seat.
-
B.
audienceCapacityType
Indicates the classification or type of capacity used to describe how many audience members a venue or event space can accommodate.
-
C.
hasSeating
Indicates that one entity provides or contains seating capacity or seating arrangements for another entity.
-
D.
hasClubSeats
Indicates that an entity (such as a venue or section) includes or is equipped with club-level seating.
-
E.
hasAuditorium
Indicates that one entity possesses or includes an auditorium as part of its facilities.
- 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_69aed94425148190be337845d56fac22 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefcae22a081908af65a960306b78c |
completed | March 9, 2026, 5 p.m. |
| PD | Predicate disambiguation | batch_69aef909c9c88190b09d48dad325a83c |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:40 p.m.