Triple
T27634795
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Temple University athletics |
E696439
|
entity |
| Predicate | homeFieldFieldHockey |
P36076
|
FINISHED |
| Object | Howarth Field |
—
|
NE NERFINISHED |
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: Howarth Field | Statement: [Temple University athletics, homeFieldFieldHockey, Howarth Field]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeFieldFieldHockey Context triple: [Temple University athletics, homeFieldFieldHockey, Howarth Field]
-
A.
homeFieldLocation
Indicates the location where an entity’s primary or home field, venue, or playing ground is situated.
-
B.
homeFieldForALTeam
Indicates that a particular stadium or ballpark serves as the designated home field for a specific American League baseball team.
-
C.
homeFieldAssociation
Indicates that one entity serves as the primary or home field, venue, or location associated with another entity.
-
D.
isHomeFieldOf
chosen
Indicates that a particular location or venue serves as the primary home field or home ground for a specific team or organization.
-
E.
denotesHomeGroundOf
Indicates that a particular location serves as the primary home ground or home venue for a specified team, organization, or entity.
- 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_69ef5909f3848190805f35b76833e722 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f63126f3e08190a32c02b24aae3c7c |
completed | May 2, 2026, 5:15 p.m. |
| PD | Predicate disambiguation | batch_69f62c1921008190a62675a31f66a875 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 2:23 p.m.