Triple
T1087513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Palais des Beaux-Arts |
E24084
|
entity |
| Predicate | eventTypeHosted |
P613
|
FINISHED |
| Object | international exhibitions |
—
|
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: international exhibitions | Statement: [Palais des Beaux-Arts, eventTypeHosted, international exhibitions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eventTypeHosted Context triple: [Palais des Beaux-Arts, eventTypeHosted, international exhibitions]
-
A.
hostsEvent
chosen
Indicates that an entity organizes and provides the venue or setting for an event to take place.
-
B.
hosted
Indicates that one entity organized and provided the venue or platform for an event, activity, or presence involving another entity.
-
C.
eventIn
Indicates that an event occurs within, or is situated in, a specific location, context, or larger event.
-
D.
eventRole
Indicates the specific function, capacity, or part an entity plays within an event or occurrence.
-
E.
eventUse
Indicates that an event involves the use or utilization of a particular entity (e.g., a resource, tool, or method) as part of its occurrence.
- 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_69a49404428c819092dcc9632f5f7b8b |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4b97c64a88190bf1119fdd4940bf3 |
completed | March 1, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69a4b7407914819092ed933a7316b450 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.