Triple
T16482472
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bad RagARTz sculpture triennial |
E400353
|
entity |
| Predicate | usesSpace |
P122947
|
FINISHED |
| Object | parks |
—
|
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: parks | Statement: [Bad RagARTz sculpture triennial, usesSpace, parks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesSpace Context triple: [Bad RagARTz sculpture triennial, usesSpace, parks]
-
A.
isWrittenWithSpace
Indicates that something is written or represented with spaces separating its components or elements.
-
B.
usesCodeSpace
Indicates that one entity employs or operates within a particular code space or coding environment provided by another entity.
-
C.
usesSpacecraft
Indicates that one entity operates, employs, or relies on a spacecraft to perform an action or fulfill a function in relation to another entity or context.
-
D.
hasSpaceType
Indicates that one entity is associated with, or classified by, a particular type or category of space.
-
E.
hasCentralSpace
Indicates that an entity includes or is characterized by a primary, central area or space within its overall structure.
- 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_69d883813098819084f5409539723b59 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e03643881908b16ddb9004af5d0 |
completed | April 18, 2026, 7:08 a.m. |
| PD | Predicate disambiguation | batch_69e22706b0588190a48a951c5211a617 |
completed | April 17, 2026, 12:26 p.m. |
| PDg | Predicate description generation | batch_69e24556c1348190902a4d116c3137d9 |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 10, 2026, 5:13 a.m.