Triple
T38362769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hey Fightin’ Tigers |
E892339
|
entity |
| Predicate | typicalLocationPerformed |
P60269
|
FINISHED |
| Object | Tiger Stadium |
E309814
|
NE 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: Tiger Stadium | Statement: [Hey Fightin’ Tigers, typicalLocationPerformed, Tiger Stadium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalLocationPerformed Context triple: [Hey Fightin’ Tigers, typicalLocationPerformed, Tiger Stadium]
-
A.
tookPlaceAtLocation
Indicates that an event or action occurred at a specific location.
-
B.
examinationLocation
Indicates the place or setting where an examination or test is conducted.
-
C.
commonlyPerformedIn
Indicates that an action or activity is typically or frequently carried out within a particular context, location, or setting.
-
D.
encounterLocation
Indicates the place or setting where two or more entities meet, interact, or come into contact.
-
E.
frequentlyPerformedAt
chosen
Indicates that an action or event occurs regularly or with high frequency at a particular location or context.
- F. None of above.
Provenance (4 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_69f76e47cb4c8190bdd92cd1db59c0c5 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41a801831c8190b5d47fea007a987a |
completed | June 28, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_6a037a1c850c819088795a7ae59bdeb8 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:31 p.m.