Triple
T2692478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Exhibition Place |
E58433
|
entity |
| Predicate | openedForFairs |
P16243
|
FINISHED |
| Object | late 19th century |
—
|
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: late 19th century | Statement: [Exhibition Place, openedForFairs, late 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedForFairs Context triple: [Exhibition Place, openedForFairs, late 19th century]
-
A.
openedForEvent
chosen
Indicates that a venue or location is made accessible and operational specifically for a particular event.
-
B.
publicExhibitOpened
Indicates that a public exhibition has been officially opened or made accessible to the general public.
-
C.
openedForPublic
Indicates that something has been made accessible or available for use, entry, or participation by the general public.
-
D.
openingWorkOf
Indicates that one work serves as the first or introductory piece in relation to another work, such as the opening item in a sequence or collection.
-
E.
openedForUse
Indicates that something has been made accessible and available for its intended operation or use.
- 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_69ab4ac269e481909cb317d79e68b75b |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abda0dd97c81909a60cf200f57c087 |
completed | March 7, 2026, 7:55 a.m. |
| PD | Predicate disambiguation | batch_69abd81ea5d88190ab5c8f8b8064b931 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:54 p.m.