Triple
T19413772
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shenzhen Concert Hall |
E485654
|
entity |
| Predicate | seatingCapacityOfChamberHall |
P21044
|
FINISHED |
| Object | about 400 |
—
|
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: about 400 | Statement: [Shenzhen Concert Hall, seatingCapacityOfChamberHall, about 400]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seatingCapacityOfChamberHall Context triple: [Shenzhen Concert Hall, seatingCapacityOfChamberHall, about 400]
-
A.
mainHallCapacity
Indicates the maximum number of people that the main hall can accommodate at one time.
-
B.
plenaryChamberCapacity
chosen
Indicates the seating capacity of the main plenary chamber where formal sessions or assemblies are held.
-
C.
seatingCapacity
Indicates the maximum number of people that something (typically a venue or vehicle) is designed or allowed to seat.
-
D.
audienceCapacityType
Indicates the classification or type of capacity used to describe how many audience members a venue or event space can accommodate.
-
E.
roomCapacity
Indicates the maximum number of people or occupants that a room is designed or allowed to hold.
- 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_69d8e8d688f881909c85104a62e09d8a |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e62af834fc81908cb176076de10c1c |
completed | April 20, 2026, 1:32 p.m. |
| PD | Predicate disambiguation | batch_69e4fd68b1f881908d273de1fee81a75 |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:37 p.m.