Triple
T19415307
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tennessee State Tigers football |
E485696
|
entity |
| Predicate | fieldSurfaceAtNissanStadium |
P12326
|
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: [Tennessee State Tigers football, fieldSurfaceAtNissanStadium, natural grass]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fieldSurfaceAtNissanStadium Context triple: [Tennessee State Tigers football, fieldSurfaceAtNissanStadium, natural grass]
-
A.
outfieldSurface
Indicates the type or condition of the playing surface specifically in the outfield area of a sports field.
-
B.
homeFieldSurface
chosen
Indicates the type of playing surface used at a team's home field or stadium.
-
C.
infieldSurface
Indicates that one entity serves as the playing surface material or type for the infield area of another entity (such as a sports field or stadium).
-
D.
surfaceAtHomeStadium
Indicates the type of playing surface present at a team's home stadium.
-
E.
fieldSide
Indicates the relative side or position of something with respect to a defined field or playing area.
- 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_69d8e8d688f881909c85104a62e09d8a |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e62af90758819088999d98d270011a |
completed | April 20, 2026, 1:32 p.m. |
| PD | Predicate disambiguation | batch_69e4fd68b1f881908d273de1fee81a75 |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:37 p.m.