Triple
T27551196
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | City of the Arts |
E695503
|
entity |
| Predicate | notableVenueHighlighted |
P113968
|
FINISHED |
| Object | Segerstrom Center for the Arts |
—
|
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: Segerstrom Center for the Arts | Statement: [City of the Arts, notableVenueHighlighted, Segerstrom Center for the Arts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableVenueHighlighted Context triple: [City of the Arts, notableVenueHighlighted, Segerstrom Center for the Arts]
-
A.
notableVenueFor
chosen
Indicates that a venue is especially recognized or significant for hosting, presenting, or being associated with a particular entity or activity.
-
B.
notableRecordingVenueFor
Indicates that a venue is particularly recognized or distinguished as the place where a specific recording was made.
-
C.
notableLocationFeatured
Indicates that a particular location is prominently highlighted or showcased in relation to the subject.
-
D.
notableSpot
Indicates that a location is recognized as a significant or noteworthy place in some context.
-
E.
notablePlace
Indicates that a place is especially significant, famous, or noteworthy in relation to the subject.
- 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_69ef5386c3e08190bfe33aa326e1f72b |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69fff09dae088190bd8460060d778feb |
completed | May 10, 2026, 2:42 a.m. |
| PD | Predicate disambiguation | batch_69fff0027c5c8190baa5c7a15852cbe0 |
completed | May 10, 2026, 2:40 a.m. |
Created at: April 27, 2026, 1:34 p.m.