Triple
T35410924
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2021 Rose Bowl |
E1023509
|
entity |
| Predicate | cityRelocatedFrom |
P31958
|
FINISHED |
| Object | Pasadena, California |
—
|
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: Pasadena, California | Statement: [2021 Rose Bowl, cityRelocatedFrom, Pasadena, California]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cityRelocatedFrom Context triple: [2021 Rose Bowl, cityRelocatedFrom, Pasadena, California]
-
A.
cityAfterRelocation
Indicates the city where an entity is located after it has been moved or relocated from a previous place.
-
B.
cityPreviouslyLocatedIn
chosen
Indicates that a city was formerly situated within a specified location or administrative region, but is no longer located there.
-
C.
locatedInOldCity
Indicates that an entity is situated within the boundaries of an old or historic part of a city.
-
D.
formerCityName
Indicates that an entity was previously known by a different city name in the past.
-
E.
relocatedTo
Indicates that an entity has moved or been transferred from its previous location to a new specified location.
- 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_69f76df54bac8190bd0d3b0eb35cda5f |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f795672b40819087ccce744e044124 |
completed | May 3, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69f7910770108190bdd39ddb5d304f54 |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 3, 2026, 4:03 p.m.