Triple
T32115968
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monster.com Park |
E820238
|
entity |
| Predicate | officialNameOfStadiumDuringMostOfHistory |
P80482
|
FINISHED |
| Object | Candlestick Park |
—
|
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: Candlestick Park | Statement: [Monster.com Park, officialNameOfStadiumDuringMostOfHistory, Candlestick Park]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officialNameOfStadiumDuringMostOfHistory Context triple: [Monster.com Park, officialNameOfStadiumDuringMostOfHistory, Candlestick Park]
-
A.
previousNameOfStadiumOfClub
Indicates that one entity is a former name previously used for the stadium belonging to a particular sports club.
-
B.
stadiumAlsoKnownAs
Indicates that a stadium has an alternative name or alias by which it is also known.
-
C.
associatedWithStadiumNameHistory
Indicates that there is a relationship between an entity and the historical or past names of a stadium with which it has been associated.
-
D.
stadiumOfficialName
chosen
Indicates the formal, legally recognized name assigned to a stadium.
-
E.
hostStadiumPreviousName
Indicates that a stadium previously had a different official name before its current one.
- 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_69f3490209c881908ec0241476715f15 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69ff0d80c0dc81909fbd12285c7a45c0 |
completed | May 9, 2026, 10:33 a.m. |
| PD | Predicate disambiguation | batch_69ff0cd03e78819094895058f925fbfa |
completed | May 9, 2026, 10:30 a.m. |
Created at: May 1, 2026, 12:28 a.m.