Triple
T35056693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deaf Valley |
E1011486
|
entity |
| Predicate | homeFieldEnvironmentOf |
P182059
|
FINISHED |
| Object | Tiger Stadium |
—
|
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: Tiger Stadium | Statement: [Deaf Valley, homeFieldEnvironmentOf, Tiger Stadium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeFieldEnvironmentOf Context triple: [Deaf Valley, homeFieldEnvironmentOf, Tiger Stadium]
-
A.
homeFieldLocation
Indicates the location where an entity’s primary or home field, venue, or playing ground is situated.
-
B.
stateOfHomeGround
Indicates the location or region that serves as an entity’s primary home ground or base of operations.
-
C.
homeGroundFeature
Indicates that a particular feature or characteristic is associated with or defines the home ground of an entity.
-
D.
homeFieldSurface
Indicates the type of playing surface used at a team's home field or stadium.
-
E.
homeFieldConfiguration
Indicates the specific arrangement or setup of a team’s home playing field or venue in relation to an event or competition.
- F. None of above. chosen
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_69f76dd09c308190a523454853ce842b |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7865578d48190bf90e470634fd97d |
completed | May 3, 2026, 5:31 p.m. |
| PD | Predicate disambiguation | batch_69f7841812f081909d878955d114088e |
completed | May 3, 2026, 5:21 p.m. |
| PDg | Predicate description generation | batch_69f78575917481909a3defd6a4c366bd |
completed | May 3, 2026, 5:27 p.m. |
Created at: May 3, 2026, 4:01 p.m.