Triple
T25008534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crown Lighter Lions |
E625918
|
entity |
| Predicate | usesBallparkType |
P130109
|
FINISHED |
| Object | outdoor baseball 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: outdoor baseball stadium | Statement: [Crown Lighter Lions, usesBallparkType, outdoor baseball stadium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesBallparkType Context triple: [Crown Lighter Lions, usesBallparkType, outdoor baseball stadium]
-
A.
usesBallparkFor
Indicates that one entity makes use of a particular ballpark facility for its activities or events.
-
B.
usesBallparkSurface
chosen
Indicates that one entity employs or is played on a particular ballpark surface as its field or playing surface.
-
C.
hasBallpark
Indicates that an entity possesses, is associated with, or includes a specific ballpark as part of its attributes or facilities.
-
D.
usesBallparksIn
Indicates that one entity makes use of or operates within specific ballparks located in a particular place or context.
-
E.
ballpark
Indicates an approximate or rough estimation of a value, rather than an exact or precise figure.
- 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_69e2ff27755881908490178e83701160 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f47b865df48190bf4b6d3e9f9305e6 |
completed | May 1, 2026, 10:08 a.m. |
| PD | Predicate disambiguation | batch_69f4682c8a3c8190adbfaac99474eaaf |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 18, 2026, 6:05 a.m.