Triple
T29402091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mazuma Stadium |
E745670
|
entity |
| Predicate | hasPitchSurface |
P168761
|
FINISHED |
| Object | 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: grass | Statement: [Mazuma Stadium, hasPitchSurface, grass]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPitchSurface Context triple: [Mazuma Stadium, hasPitchSurface, grass]
-
A.
usesBallparkSurface
Indicates that one entity employs or is played on a particular ballpark surface as its field or playing surface.
-
B.
outfieldSurface
Indicates the type or condition of the playing surface specifically in the outfield area of a sports field.
-
C.
hasPitch
Indicates that one entity possesses or is characterized by a specific pitch (such as a tonal, acoustic, or frequency-related property).
-
D.
hasPitchType
Indicates that an entity is associated with, or characterized by, a specific type or category of pitch.
-
E.
hasCourtSurface
Indicates that something (such as a court or playing area) possesses a specific type of surface.
- 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_69f0a79eb7d081908c67197a5f347e68 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f67805551c81909e016ae9e3031076 |
completed | May 2, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69f675ff62c48190a634bbb8896973b9 |
completed | May 2, 2026, 10:09 p.m. |
| PDg | Predicate description generation | batch_69f676f73c3481909f01fa69851b7298 |
completed | May 2, 2026, 10:13 p.m. |
Created at: April 28, 2026, 2:51 p.m.