Triple
T17786691
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kiss (Tino Sehgal) |
E444033
|
entity |
| Predicate | referencedDomain |
P41143
|
FINISHED |
| Object | art history |
—
|
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: art history | Statement: [Kiss (Tino Sehgal), referencedDomain, art history]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: referencedDomain Context triple: [Kiss (Tino Sehgal), referencedDomain, art history]
-
A.
involvedDomain
Indicates that an entity participates in or is associated with a particular domain, field, or area of activity.
-
B.
indicatesDomain
chosen
Indicates a domain or area of knowledge, activity, or applicability to which something (such as a concept, resource, or entity) belongs or is relevant.
-
C.
recognizedAsDomain
Indicates that one entity is acknowledged or accepted as a valid or authoritative domain associated with another entity.
-
D.
affectedDomain
Indicates the domain, field, or area that is impacted or influenced by a given action, event, or condition.
-
E.
containsDomain
Indicates that one entity includes or encompasses a specific domain as part of its scope, structure, or area of applicability.
- 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_69d8b9ef17708190bdf7e2adbf14ddc2 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e487938418819096016ad717b014e6 |
completed | April 19, 2026, 7:43 a.m. |
| PD | Predicate disambiguation | batch_69e3d8d8e538819084f1584426b41d5e |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:12 a.m.