Triple
T10972830
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Matt Sullivan |
E259284
|
entity |
| Predicate | makesBetWith |
P27042
|
FINISHED |
| Object | coworkers |
—
|
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: coworkers | Statement: [Matt Sullivan, makesBetWith, coworkers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: makesBetWith Context triple: [Matt Sullivan, makesBetWith, coworkers]
-
A.
betting
chosen
Indicates engaging in a wager where one party risks something of value on the outcome of an uncertain event involving another entity.
-
B.
bettingOdds
Indicates the likelihood or probability of a particular outcome in a bet, typically expressed as numerical odds set for wagering.
-
C.
typeOfStake
Indicates the specific kind or category of stake or ownership interest that one entity holds in another.
-
D.
hasToteBetting
Indicates that an entity offers or is associated with pari-mutuel (tote) betting services or facilities.
-
E.
coinTossParticipant
Indicates that an entity takes part in a coin toss event, either as the initiator or as one of the involved participants.
- 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_69d6aa895f4c8190887a15460ef622f4 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7719c16648190ab5a87abb1c61990 |
completed | April 9, 2026, 9:30 a.m. |
| PD | Predicate disambiguation | batch_69d72e8c27cc81908050590b7a04cafd |
completed | April 9, 2026, 4:43 a.m. |
Created at: April 8, 2026, 9:24 p.m.