Triple
T30076214
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Big Sweep |
E764326
|
entity |
| Predicate | installedOutside |
P168416
|
FINISHED |
| Object | Denver Art Museum |
—
|
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: Denver Art Museum | Statement: [Big Sweep, installedOutside, Denver Art Museum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: installedOutside Context triple: [Big Sweep, installedOutside, Denver Art Museum]
-
A.
installedNear
Indicates that one entity is installed in physical proximity to another entity, typically within a short, functionally relevant distance.
-
B.
installedFor
Indicates that something has been set up or put in place to be used by or on behalf of a particular entity.
-
C.
installedAt
Indicates that something has been set up, placed, or put into operation at a specific location or site.
-
D.
installedBy
Indicates that one entity was set up, put in place, or made operational through the actions or intervention of another entity.
-
E.
installedAfter
Indicates that one installation event occurred later in time than another installation event.
- F. None of above. chosen
Provenance (4 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_69f22472eee081909791dc372aa766e9 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67d3da1608190aaf738cc69b73c26 |
completed | May 2, 2026, 10:39 p.m. |
| PD | Predicate disambiguation | batch_69f673c664f08190b4d66cdc305e10db |
completed | May 2, 2026, 9:59 p.m. |
| PDg | Predicate description generation | batch_69f6749f205c81909d1aacf462912eee |
completed | May 2, 2026, 10:03 p.m. |
Created at: April 29, 2026, 7:02 p.m.