Triple
T35587630
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bobcats |
E1028400
|
entity |
| Predicate | homeSoccerComplex |
P67968
|
FINISHED |
| Object | Bobcat Soccer Complex |
—
|
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: Bobcat Soccer Complex | Statement: [Bobcats, homeSoccerComplex, Bobcat Soccer Complex]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeSoccerComplex Context triple: [Bobcats, homeSoccerComplex, Bobcat Soccer Complex]
-
A.
homeSoccerField
chosen
Indicates that a particular soccer field serves as the designated home field for a given team or organization.
-
B.
sportsInfrastructureDevelopedFor
Indicates that sports-related facilities or structures have been created, improved, or established for the benefit or use of a particular entity.
-
C.
homeCompetitionZone
Indicates that a competition or event takes place in the home zone or home territory associated with a particular participant or entity.
-
D.
homeStadiumFeatureOf
Indicates that a stadium serves as the designated home venue or primary hosting facility for a particular team, club, or organization.
-
E.
surfaceAtHomeStadium
Indicates the type of playing surface present at a team's home stadium.
- 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_69f76e0495a081909beced418558c0b4 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7b0e5744c8190a22c1e1d6fcfa466 |
completed | May 3, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f7ab70d034819080295628497d8582 |
completed | May 3, 2026, 8:09 p.m. |
Created at: May 3, 2026, 4:04 p.m.