Triple
T27983866
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frieze Art Fair |
E706693
|
entity |
| Predicate | hasSisterEvent |
P114562
|
FINISHED |
| Object | Frieze Masters |
—
|
NE NERFINISHED |
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: Frieze Masters | Statement: [Frieze Art Fair, hasSisterEvent, Frieze Masters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSisterEvent Context triple: [Frieze Art Fair, hasSisterEvent, Frieze Masters]
-
A.
hasCompanionEvent
chosen
Indicates that one event is associated with another event that occurs alongside it as a related or accompanying occurrence.
-
B.
sisterFestivalOf
Indicates a relationship where two festivals are formally recognized as counterparts or partners, often sharing similar themes, origins, or collaborative ties.
-
C.
hasSister
Indicates that one entity is the sister of another entity.
-
D.
sisterConference
Indicates that two conferences are related as sister events, typically sharing similar themes, organizers, or structures while remaining distinct occurrences.
-
E.
hasEventSeries
Indicates that an entity is associated with, or participates in, a sequence of related events forming a series.
- 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_69ef96b8b8d88190bad5e4ae966bf14e |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f6e6029a10819098ff21f58079e70e |
completed | May 3, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d5e8188190b1e1c2e5d1b77031 |
completed | May 3, 2026, 5:57 a.m. |
Created at: April 27, 2026, 7:46 p.m.