Triple
T18010654
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baylor Bears baseball |
E430867
|
entity |
| Predicate | usesBallparkSurface |
P130109
|
FINISHED |
| Object | natural grass |
—
|
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: natural grass | Statement: [Baylor Bears baseball, usesBallparkSurface, natural grass]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesBallparkSurface Context triple: [Baylor Bears baseball, usesBallparkSurface, natural grass]
-
A.
usesBallparkFor
Indicates that one entity makes use of a particular ballpark facility for its activities or events.
-
B.
hasBallpark
Indicates that an entity possesses, is associated with, or includes a specific ballpark as part of its attributes or facilities.
-
C.
usesBallSport
Indicates that an activity or event involves the use of a ball as part of a sport.
-
D.
ballpark
Indicates an approximate or rough estimation of a value, rather than an exact or precise figure.
-
E.
usesBallShape
Indicates that one entity employs or incorporates a ball-like (spherical) shape in its form, design, or operation.
- 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_69d8b904530081908bf341d842464856 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4b51f0a488190bd34e1f9039f4dc9 |
completed | April 19, 2026, 10:57 a.m. |
| PD | Predicate disambiguation | batch_69e3f90039e4819080527f860dca042e |
completed | April 18, 2026, 9:34 p.m. |
| PDg | Predicate description generation | batch_69e42d8d68288190a05dc5d7803cf823 |
completed | April 19, 2026, 1:19 a.m. |
Created at: April 10, 2026, 10:24 a.m.