Triple
T303849
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | American League Division Series |
E6254
|
entity |
| Predicate | homeFieldAdvantage |
P11326
|
FINISHED |
| Object | higher-seeded team |
—
|
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: higher-seeded team | Statement: [American League Division Series, homeFieldAdvantage, higher-seeded team]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeFieldAdvantage Context triple: [American League Division Series, homeFieldAdvantage, higher-seeded team]
-
A.
homeFieldLocation
Indicates the location where an entity’s primary or home field, venue, or playing ground is situated.
-
B.
homeFieldOpened
Indicates that a team's designated home field has officially begun operation or been opened for use.
-
C.
homeTeam
Indicates that one entity is designated as the home team in a game, match, or sporting event involving another entity.
-
D.
homeLeague
Indicates that a sports team primarily competes in, or is officially associated with, a particular league as its main organizational affiliation.
-
E.
homeStadium
Indicates that a particular stadium serves as the primary venue where a sports team plays its home games.
- 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_69a2e79230508190b912ecb555aae17e |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2ea2fba548190a5aeb1597dca96bd |
completed | Feb. 28, 2026, 1:14 p.m. |
| PD | Predicate disambiguation | batch_69a2e93c367881908d3f6e2b81d44d7f |
completed | Feb. 28, 2026, 1:10 p.m. |
| PDg | Predicate description generation | batch_69a2ea2af1388190b93235602ace679e |
completed | Feb. 28, 2026, 1:14 p.m. |
Created at: Feb. 28, 2026, 1:06 p.m.