Triple
T25662846
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Art Pavilion in Zagreb |
E643431
|
entity |
| Predicate | hasExhibitionSpaceArea |
P9481
|
FINISHED |
| Object | approximately 600 square metres |
—
|
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 600 square metres | Statement: [Art Pavilion in Zagreb, hasExhibitionSpaceArea, approximately 600 square metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasExhibitionSpaceArea Context triple: [Art Pavilion in Zagreb, hasExhibitionSpaceArea, approximately 600 square metres]
-
A.
hasExhibitionArea
chosen
Indicates that an entity includes or provides a designated space or area for exhibitions or displays.
-
B.
exhibitionSpaceType
Indicates the specific kind or category of space used to display or present exhibitions.
-
C.
hasExhibitionVenue
Indicates that an exhibition is held or hosted at a particular venue.
-
D.
hasExhibitionScope
Indicates the thematic, geographic, temporal, or conceptual range and boundaries that define what an exhibition covers.
-
E.
hasExhibitionVenueType
Indicates the type or category of venue where an exhibition is held or presented.
- 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_69e77e7e45648190a068ed3faa8016ea |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6640168948190811bd5f933a87cf5 |
completed | May 2, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69f6633451948190bcc0410602bb4914 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 21, 2026, 6:57 p.m.