Triple
T586092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fred Clarke |
E15159
|
entity |
| Predicate | strategySpecialty |
P13768
|
FINISHED |
| Object | aggressive baserunning |
—
|
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: aggressive baserunning | Statement: [Fred Clarke, strategySpecialty, aggressive baserunning]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: strategySpecialty Context triple: [Fred Clarke, strategySpecialty, aggressive baserunning]
-
A.
coachingSpecialty
chosen
Indicates that a coach focuses on or is specialized in a particular area, topic, or type of coaching.
-
B.
tactic
Indicates a strategic method or maneuver employed by one entity to influence, counter, or gain advantage over another in a specific context.
-
C.
hasSpecialty
Indicates that an entity possesses a particular area of expertise, focus, or professional specialization.
-
D.
specialComposition
Indicates that one entity is composed of another in a distinctive or non-standard way, highlighting a particular or exceptional form of composition between them.
-
E.
missionFocus
Indicates that an entity’s primary attention, effort, or resources are directed toward a particular mission, goal, or objective.
- 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_69a4935783b8819082b77726ec10cc42 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49b9a46388190a094b9ebf8dec397 |
completed | March 1, 2026, 8:03 p.m. |
| PD | Predicate disambiguation | batch_69a494ca68448190a516b9c3525d8916 |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:33 p.m.