Triple
T6805044
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ferguson Arthur Jenkins |
E156281
|
entity |
| Predicate | hasSignaturePitch |
P38697
|
FINISHED |
| Object | fastball |
—
|
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: fastball | Statement: [Ferguson Arthur Jenkins, hasSignaturePitch, fastball]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSignaturePitch Context triple: [Ferguson Arthur Jenkins, hasSignaturePitch, fastball]
-
A.
hasPitch
Indicates that one entity possesses or is characterized by a specific pitch (such as a tonal, acoustic, or frequency-related property).
-
B.
hasSignatureSong
Indicates that an artist or performer is especially associated with a particular song that is widely recognized as their defining or most iconic work.
-
C.
hasPitchLength
Indicates that an entity (such as a field or pitch) is associated with a specific measurement of its length.
-
D.
hasSignaturePerformanceBy
Indicates that something features a standout or defining performance delivered by a particular performer.
-
E.
hasPitchType
chosen
Indicates that an entity is associated with, or characterized by, a specific type or category of pitch.
- 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_69c68826e6a48190a3d220b541e639de |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d2ea459c819095388218d53c250a |
completed | March 27, 2026, 6:56 p.m. |
| PD | Predicate disambiguation | batch_69c6d099bf08819089a9f9894d037e74 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:16 p.m.