Triple
T18096135
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toyota Field |
E433089
|
entity |
| Predicate | classificationOfHomeTeam |
P124525
|
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: [Toyota Field, classificationOfHomeTeam, Double-A]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: classificationOfHomeTeam Context triple: [Toyota Field, classificationOfHomeTeam, Double-A]
-
A.
hasHomeTeamType
chosen
Indicates that an entity has a specified classification or category for its home team (e.g., type or role of the home team in a competition).
-
B.
homeTeam
Indicates that one entity is designated as the home team in a game, match, or sporting event involving another entity.
-
C.
homeFieldForALTeam
Indicates that a particular stadium or ballpark serves as the designated home field for a specific American League baseball team.
-
D.
locationTeam1Home
Indicates that the specified location serves as the home venue or home ground for team 1 in the relationship.
-
E.
locationTeam2Home
Indicates that the specified location serves as the home venue or home ground for the second team involved in the context.
- 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_69d8b907d05c819083cc3bd6021089e6 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4dd1c56848190be0b8c80b30dba6c |
completed | April 19, 2026, 1:48 p.m. |
| PD | Predicate disambiguation | batch_69e4330e1f2881908b2506d47c48736b |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:27 a.m.