Triple
T9628195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bee Hive |
E232524
|
entity |
| Predicate | operatedAsHomeFieldFor |
P36076
|
FINISHED |
| Object | Major League Baseball games |
—
|
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: Major League Baseball games | Statement: [Bee Hive, operatedAsHomeFieldFor, Major League Baseball games]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedAsHomeFieldFor Context triple: [Bee Hive, operatedAsHomeFieldFor, Major League Baseball games]
-
A.
playedHomeGamesFrom
Indicates the time period during which a team or player hosted their home games at a particular venue.
-
B.
playsHomeGamesOn
Indicates that an entity regularly hosts its home games or matches at a specified location or venue.
-
C.
isHomeFieldOf
chosen
Indicates that a particular location or venue serves as the primary home field or home ground for a specific team or organization.
-
D.
homeFieldSince
Indicates that a particular location has served as the designated home field or home venue for an entity starting from a specified point in time.
-
E.
playedHomeGamesUntil
Indicates the period up to which a team or player hosted their home games at a particular venue.
- 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_69ca848793ec8190a93a12383a754dc0 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9afeb64c8190be91024c2e9039d3 |
completed | April 1, 2026, 10:23 p.m. |
| PD | Predicate disambiguation | batch_69ccd5acfa5c8190aaba3cf548723604 |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:10 p.m.