Triple
T26072525
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TEFAF Maastricht |
E657586
|
entity |
| Predicate | hasSisterFair |
P126083
|
FINISHED |
| Object | TEFAF New York |
—
|
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: TEFAF New York | Statement: [TEFAF Maastricht, hasSisterFair, TEFAF New York]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSisterFair Context triple: [TEFAF Maastricht, hasSisterFair, TEFAF New York]
-
A.
sisterFestivalOf
chosen
Indicates a relationship where two festivals are formally recognized as counterparts or partners, often sharing similar themes, origins, or collaborative ties.
-
B.
hasSister
Indicates that one entity is the sister of another entity.
-
C.
hasSisterResort
Indicates that one resort is formally associated with another as its sister property, typically under common ownership or branding.
-
D.
sisterVenue
Indicates that two venues are related as peers or counterparts, typically sharing ownership, branding, or affiliation without one being subordinate to the other.
-
E.
hasSisterCommunity
Indicates a formal or recognized partnership relationship between two communities, often for mutual support, exchange, or collaboration.
- 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_69ee5bbe539081909efc7f9dd7c1b53c |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c1f94ac8190bc6fbc7916fc0d82 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 26, 2026, 7:30 p.m.