Triple
T10776332
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brig Owens |
E254206
|
entity |
| Predicate | postSportsCareer |
P24096
|
FINISHED |
| Object | attorney |
—
|
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: attorney | Statement: [Brig Owens, postSportsCareer, attorney]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postSportsCareer Context triple: [Brig Owens, postSportsCareer, attorney]
-
A.
sportsCareer
Indicates a relationship where an entity’s professional involvement, roles, or achievements in sports are associated with a particular sport, team, period, or competitive level.
-
B.
postPlayingCareer
chosen
Indicates a relationship where something pertains to or occurs during an entity’s period after its playing career has ended.
-
C.
sportsAchievement
Indicates a relationship where an entity attains or is recognized for a notable accomplishment in a sports context.
-
D.
careerOPS
Indicates a relationship where an entity’s career on-base plus slugging (OPS) statistic is recorded or associated with that entity.
-
E.
hasPlayedProfessionalSports
Indicates that an entity has participated as an athlete in an officially recognized professional-level sports competition or league.
- 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_69d6aa609f008190a294200aefcb7bd5 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7329d8c908190bddad40685133ea1 |
completed | April 9, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69d6f31455648190b5c24690487b1b54 |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:16 p.m.