Triple
T13446372
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pop Fisher |
E320494
|
entity |
| Predicate | settingSportLevel |
P24551
|
FINISHED |
| Object | professional baseball |
—
|
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: professional baseball | Statement: [Pop Fisher, settingSportLevel, professional baseball]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: settingSportLevel Context triple: [Pop Fisher, settingSportLevel, professional baseball]
-
A.
governsSportLevel
Indicates that one entity has authority to set, control, or regulate the competitive level or tier at which a sport or sporting activity is conducted.
-
B.
representsSportLevel
chosen
Indicates that an entity participates in or is associated with a particular level or tier within a sport.
-
C.
associatedLeagueLevel
Indicates that one entity is linked to another entity representing the competitive tier or level of a sports league.
-
D.
competitionLevel
Indicates the degree or intensity of competitive pressure or rivalry present in a given context or interaction.
-
E.
supportsLeagueLevel
Indicates that one entity provides the necessary conditions, resources, or authorization for a particular league level to exist or operate.
- 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_69d80761e6cc8190a90c844589998ecc |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbaef5f610819092cad33ef72075ff |
completed | April 12, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69d9a03ce03481908c61094f0cc0c158 |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:40 p.m.