Triple
T26008312
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jeffrey Maier |
E646820
|
entity |
| Predicate | laterWorkedIn |
P17879
|
FINISHED |
| Object | sports marketing |
—
|
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: sports marketing | Statement: [Jeffrey Maier, laterWorkedIn, sports marketing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterWorkedIn Context triple: [Jeffrey Maier, laterWorkedIn, sports marketing]
-
A.
laterWorksAt
Indicates that an entity begins working at a place or organization at a time later than another referenced time or employment situation.
-
B.
hasWorkedIn
chosen
Indicates that a person has been employed or has performed work within a particular organization, location, or domain for some period of time.
-
C.
workedAs
Indicates that an entity held a particular job, role, or position, performing work in that capacity.
-
D.
laterWorksAs
Indicates that an entity holds or takes on a particular occupation or role at a later point in time relative to another referenced time or role.
-
E.
laterCareerWorkOf
Indicates that one work represents a creator’s later career output in relation to another work or to their overall body of work.
- 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_69e77e89d5848190b54352cdb74f6029 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f70e8755a48190931eaa77946f9460 |
completed | May 3, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f70abc00848190a1c3f495ef6c8dc6 |
completed | May 3, 2026, 8:43 a.m. |
Created at: April 22, 2026, 9:01 a.m.