Triple
T807415
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Comiskey Park |
E17468
|
entity |
| Predicate | siteCurrentlyUsedAs |
P16008
|
FINISHED |
| Object | parking lot for Guaranteed Rate Field |
—
|
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: parking lot for Guaranteed Rate Field | Statement: [Comiskey Park, siteCurrentlyUsedAs, parking lot for Guaranteed Rate Field]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: siteCurrentlyUsedAs Context triple: [Comiskey Park, siteCurrentlyUsedAs, parking lot for Guaranteed Rate Field]
-
A.
currentSiteUse
chosen
Indicates how a site is presently being used or the function it currently serves.
-
B.
siteTypeServed
Indicates the type of site or location that is served, supported, or handled by a given entity or resource.
-
C.
site
Indicates that one entity is the physical or virtual location where another entity is situated, occurs, or is based.
-
D.
typeOfSite
Indicates the specific category or kind of site that an entity is classified as.
-
E.
designationUsedFor
Indicates that a particular name, label, or title is employed to refer to or identify a specific entity or role.
- 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_69a4937ae8a08190b5084a03d532b30e |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4ac07fedc8190ab05595f25c1792f |
completed | March 1, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69a4aa7221c081908068e66fe720f26d |
completed | March 1, 2026, 9:06 p.m. |
Created at: March 1, 2026, 7:38 p.m.