Triple
T1258959
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Knoxville Convention Center |
E12454
|
entity |
| Predicate | ballroomSpace |
P26321
|
FINISHED |
| Object | approximately 27,000 square feet |
—
|
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: approximately 27,000 square feet | Statement: [Knoxville Convention Center, ballroomSpace, approximately 27,000 square feet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ballroomSpace Context triple: [Knoxville Convention Center, ballroomSpace, approximately 27,000 square feet]
-
A.
balletType
Indicates that one entity is classified as a specific type or category of ballet in relation to another entity.
-
B.
venue
Indicates the place or location where an event, activity, or interaction takes place.
-
C.
danceProp
Indicates that one entity is used or involved as a prop in another entity’s dance performance or dancing activity.
-
D.
exhibitionSpaceType
Indicates the specific kind or category of space used to display or present exhibitions.
-
E.
modernStage
Indicates that something functions as or is recognized as a contemporary or up-to-date stage or phase within a broader process, development, or sequence.
- F. None of above. chosen
Provenance (4 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_69a4933352e08190ac617291985e76c0 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4bfc3a2848190891e73b351019d5b |
completed | March 1, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69a4bb6eefbc81908dddd7d2ef368186 |
completed | March 1, 2026, 10:19 p.m. |
| PDg | Predicate description generation | batch_69a4bd98b62c8190a5f6710345c0537d |
completed | March 1, 2026, 10:28 p.m. |
Created at: March 1, 2026, 7:50 p.m.