Triple
T3940666
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ewing Kauffman |
E92024
|
entity |
| Predicate | positionInSportsTeam |
P13665
|
FINISHED |
| Object | principal owner of the Kansas City Royals |
—
|
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: principal owner of the Kansas City Royals | Statement: [Ewing Kauffman, positionInSportsTeam, principal owner of the Kansas City Royals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInSportsTeam Context triple: [Ewing Kauffman, positionInSportsTeam, principal owner of the Kansas City Royals]
-
A.
roleAtSportsTeam
chosen
Indicates the specific position or function an individual holds within a sports team.
-
B.
clubPosition
Indicates the specific role or position an individual holds within a sports club or team.
-
C.
positionInLineup
Indicates the specific ordered place an entity occupies within a lineup or sequence of entities.
-
D.
playsInPosition
Indicates that an entity (typically a player) performs or operates in a specific role or position within a game, sport, or activity.
-
E.
positionInLeagueSystem
Indicates the rank or tier an entity holds within an organized league or competitive system.
- 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_69aed965502c8190904ebad1203a4ae8 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeedfc88e4819084adefb695b975c5 |
completed | March 9, 2026, 3:57 p.m. |
| PD | Predicate disambiguation | batch_69aee7625ad4819097e4e8a168c19274 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:24 p.m.