Triple
T26865219
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dries Van Noten |
E676445
|
entity |
| Predicate | hasNotableShowLocation |
P67565
|
FINISHED |
| Object | Paris |
—
|
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: Paris | Statement: [Dries Van Noten, hasNotableShowLocation, Paris]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableShowLocation Context triple: [Dries Van Noten, hasNotableShowLocation, Paris]
-
A.
hasNotableShow
Indicates that an entity is associated with a particular show that is considered notable or significant.
-
B.
notableShowLocation
chosen
Indicates that a show or performance is notably associated with, took place at, or is best known for occurring in a particular location.
-
C.
hasResidentShowLocation
Indicates that a location is the regular or primary venue where a resident show is held.
-
D.
hasNotableLocationAssociation
Indicates that there is a significant or noteworthy connection between an entity and a specific location.
-
E.
hasProminentLocation
Indicates that an entity occupies a highly visible, central, or otherwise notable position within a given space or context.
- 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_69eee9ba94bc8190b44c5d4397d04ecd |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69fdec5ffe088190ac5505f26c6cff18 |
completed | May 8, 2026, 2 p.m. |
| PD | Predicate disambiguation | batch_69fdeae15f1c81908fc63fbc1b028d2e |
completed | May 8, 2026, 1:53 p.m. |
Created at: April 27, 2026, 5:28 a.m.