Triple
T779931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kauffman Stadium |
E16472
|
entity |
| Predicate | typeOfField |
P4541
|
FINISHED |
| Object | asymmetrical outfield dimensions |
—
|
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: asymmetrical outfield dimensions | Statement: [Kauffman Stadium, typeOfField, asymmetrical outfield dimensions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfField Context triple: [Kauffman Stadium, typeOfField, asymmetrical outfield dimensions]
-
A.
fieldType
chosen
Indicates the classification or category that defines the nature or kind of a given field within a structure or context.
-
B.
typeOf
Indicates that one entity is a specific kind, class, or category instance of another more general entity.
-
C.
typeOfAnnotation
Indicates that one entity is an annotation and specifies the kind or category of that annotation in relation to the annotated item.
-
D.
typeOfDate
Indicates that one entity specifies the category or kind of date (e.g., start date, end date, due date) that characterizes another date-related entity or value.
-
E.
typeOfBody
Indicates that one entity is the classification or kind of physical body that the other entity is.
- 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_69a4936ad1fc81908f190208059ccf78 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a90365648190ace53b0f0e87aa68 |
completed | March 1, 2026, 9 p.m. |
| PD | Predicate disambiguation | batch_69a4a50bd23081908908235b8ec9201e |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.