Triple
T18300248
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Somerset Patriots |
E438339
|
entity |
| Predicate | hasBallparkCapacityCategory |
P131254
|
FINISHED |
| Object | minor league-sized stadium |
—
|
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: minor league-sized stadium | Statement: [Somerset Patriots, hasBallparkCapacityCategory, minor league-sized stadium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBallparkCapacityCategory Context triple: [Somerset Patriots, hasBallparkCapacityCategory, minor league-sized stadium]
-
A.
homeBallparkCapacityApprox
Indicates that the relationship specifies an approximate seating capacity of a team's home ballpark.
-
B.
hasBallpark
Indicates that an entity possesses, is associated with, or includes a specific ballpark as part of its attributes or facilities.
-
C.
cityStadiumCapacity
Indicates the maximum number of spectators that a given city’s stadium can accommodate.
-
D.
stadiumCapacityApprox
Indicates an approximate number of people that a stadium can accommodate.
-
E.
stadiumCapacityContext
Indicates the seating capacity of a stadium as it applies within a specific contextual scope (such as time, event, or configuration).
- 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_69d8b915e3e881909125d760c15d0c29 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e5017e88cc8190a969eb628ca1b496 |
completed | April 19, 2026, 4:23 p.m. |
| PD | Predicate disambiguation | batch_69e44fdf43d08190bbcfb6b1fe3cc0ee |
completed | April 19, 2026, 3:45 a.m. |
| PDg | Predicate description generation | batch_69e451a0ba208190a5fe92832a8f7a49 |
completed | April 19, 2026, 3:53 a.m. |
Created at: April 10, 2026, 10:35 a.m.