Triple
T16764123
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Corpus Christi Hooks |
E407418
|
entity |
| Predicate | ballparkOpenedForTeam |
P124552
|
FINISHED |
| Object | Whataburger Field in 2005 |
—
|
LITERAL 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: Whataburger Field in 2005 | Statement: [Corpus Christi Hooks, ballparkOpenedForTeam, Whataburger Field in 2005]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ballparkOpenedForTeam Context triple: [Corpus Christi Hooks, ballparkOpenedForTeam, Whataburger Field in 2005]
-
A.
ballparkOpeningYear
Indicates the calendar year in which a ballpark first officially opened for use.
-
B.
ballparkLocatedOn
Indicates that a ballpark is situated on or directly associated with a specific street, road, or thoroughfare.
-
C.
ballparkNameAtTime
Indicates the name a ballpark had during a specified time or time interval.
-
D.
ballparkCity
Indicates that a ballpark is located in a particular city.
-
E.
homeBallparkCapacityApprox
Indicates that the relationship specifies an approximate seating capacity of a team's home ballpark.
- 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_69d8839174188190909f190097207065 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3abef492c8190880d3b39c3641eed |
completed | April 18, 2026, 4:06 p.m. |
| PD | Predicate disambiguation | batch_69e319cbd79c8190a03587a61c18bec0 |
completed | April 18, 2026, 5:42 a.m. |
| PDg | Predicate description generation | batch_69e326bac94481908c082117553320f8 |
completed | April 18, 2026, 6:37 a.m. |
Created at: April 10, 2026, 5:21 a.m.