Triple
T20970529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uptown, Seattle |
E516479
|
entity |
| Predicate | hasArtsFunction |
P60146
|
FINISHED |
| Object | performance venues |
—
|
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: performance venues | Statement: [Uptown, Seattle, hasArtsFunction, performance venues]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasArtsFunction Context triple: [Uptown, Seattle, hasArtsFunction, performance venues]
-
A.
hasArtFacilities
Indicates that an entity provides or is equipped with facilities or resources dedicated to art-related activities.
-
B.
hasCulturalFunction
Indicates that something serves a particular role, purpose, or function within a culture or cultural context.
-
C.
hasCulturalCenterFunction
Indicates that something serves the role or performs the activities of a cultural center, such as hosting cultural events, programs, or services.
-
D.
hasArtScene
chosen
Indicates that a place or community possesses an active or notable community of artistic activity, events, and institutions.
-
E.
hasArtCenter
Indicates that an entity possesses, hosts, or includes an art center as one of its facilities or components.
- 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_69e0b4fee5ac8190875fa9ceba1a5e5e |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6fb9f53e88190847f93e0bbca6ea0 |
completed | April 21, 2026, 4:22 a.m. |
| PD | Predicate disambiguation | batch_69e5dbe6976081908abd4e9c8734bae9 |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 1:43 p.m.