Triple
T30932688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Date My Mom |
E788037
|
entity |
| Predicate | hasContestantRole |
P192073
|
FINISHED |
| Object | single dater |
—
|
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: single dater | Statement: [Date My Mom, hasContestantRole, single dater]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasContestantRole Context triple: [Date My Mom, hasContestantRole, single dater]
-
A.
hasEntrantRole
chosen
Indicates that an entity participates in an event, competition, or process specifically in the capacity of an entrant or participant.
-
B.
hasNotableContestant
Indicates that an entity (such as a competition, show, or event) includes or is associated with a contestant who is notable or distinguished in some way.
-
C.
hasPlayingRole
Indicates that an entity participates in an activity, event, or performance in a specific playing role or capacity.
-
D.
contestantOn
Indicates that one entity participates as a competitor in a contest, show, or competition associated with another entity.
-
E.
belongsToContest
Indicates that an entity is a participant in, or is associated as an entry with, a specific contest.
- 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_69f224c0b7fc819090cb89df60d23653 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a01ac8b4ac881908aa52079c985ddac |
completed | May 11, 2026, 10:16 a.m. |
| PD | Predicate disambiguation | batch_6a01aa7fa7b48190b4911aa6bcabe7eb |
completed | May 11, 2026, 10:07 a.m. |
Created at: April 29, 2026, 8:52 p.m.