Triple
T17087338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crosby Beach |
E414631
|
entity |
| Predicate | sculptureInstallationType |
P25695
|
FINISHED |
| Object | permanent public art |
—
|
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: permanent public art | Statement: [Crosby Beach, sculptureInstallationType, permanent public art]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sculptureInstallationType Context triple: [Crosby Beach, sculptureInstallationType, permanent public art]
-
A.
featuresSculptureOf
Indicates that one entity includes or displays a sculpture that depicts or represents another entity.
-
B.
artStyleOfEnclosingSculpture
Indicates that one entity specifies the artistic style or aesthetic category of a surrounding or enclosing sculpture associated with another entity.
-
C.
isOutdoorSculpture
Indicates that the entity is a sculpture specifically designed, created, or installed for display in an outdoor environment.
-
D.
hasSculptureType
chosen
Indicates that an entity is associated with a sculpture and specifies the type or category of that sculpture.
-
E.
sculptureParkName
Indicates that a sculpture park has the specified name.
- 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_69d886cef44c8190ba56c44b4e863e64 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dbe7ccb48190b8fb39e2a0ba0782 |
completed | April 18, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69e35d67b14481909fcdbdeaa5c34785 |
completed | April 18, 2026, 10:31 a.m. |
Created at: April 10, 2026, 5:35 a.m.