Triple
T1956227
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boston Convention and Exhibition Center |
E42274
|
entity |
| Predicate | meetingSpaceArea |
P26410
|
FINISHED |
| Object | 160000 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: 160000 square feet | Statement: [Boston Convention and Exhibition Center, meetingSpaceArea, 160000 square feet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: meetingSpaceArea Context triple: [Boston Convention and Exhibition Center, meetingSpaceArea, 160000 square feet]
-
A.
hasConferenceSpace
Indicates that an entity provides or includes dedicated space suitable for holding conferences, meetings, or similar gatherings.
-
B.
hasFloorArea
Indicates that an entity possesses a specified amount of floor space as a measurable area.
-
C.
areaBControl
Indicates that one entity has control or authority over a specific region or area labeled as B.
-
D.
roofArea
Indicates the total surface area covered by the roof of a structure.
-
E.
venueArea
chosen
Indicates the physical size or spatial extent of a venue, typically measured in units such as square meters or square feet.
- 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_69a8870eea088190a38781990812a9bc |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb37b4a38819099f98be92be91ade |
completed | March 7, 2026, 5:11 a.m. |
| PD | Predicate disambiguation | batch_69abaff3eda88190b643994cb4dfb8df |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:36 p.m.