Triple
T9881949
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FirstEnergy Stadium (Reading) |
E180828
|
entity |
| Predicate | hasHomeTeamLevel |
P91588
|
FINISHED |
| Object | Double-A |
—
|
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: Double-A | Statement: [FirstEnergy Stadium (Reading), hasHomeTeamLevel, Double-A]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHomeTeamLevel Context triple: [FirstEnergy Stadium (Reading), hasHomeTeamLevel, Double-A]
-
A.
ownedTeamHomeState
Indicates that the owning entity’s home or primary location is in the same state as the team’s home state.
-
B.
isHomeFieldOf
Indicates that a particular location or venue serves as the primary home field or home ground for a specific team or organization.
-
C.
hasHomeCountryLeague
Indicates that an entity (typically a sports team or player) is associated with a specific league that operates in its home country.
-
D.
hasHostStadiumTeam
Indicates that a particular team is the primary host or home team for events held at a given stadium.
-
E.
homeTeamChampion
Indicates that the team playing at home is the champion or title-holding team in the given context.
- 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_69ca828082cc8190a40f8d299caa6545 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cdb418417c8190b00dea8916a2e102 |
completed | April 2, 2026, 12:11 a.m. |
| PD | Predicate disambiguation | batch_69cd1d810ed48190a252b70e9390c8f3 |
completed | April 1, 2026, 1:28 p.m. |
| PDg | Predicate description generation | batch_69cd36f112bc81908b473787e702de2f |
completed | April 1, 2026, 3:17 p.m. |
Created at: March 30, 2026, 8:38 p.m.