Triple
T32694736
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moms I’d Like to Follow |
E835974
|
entity |
| Predicate | recasts |
P173869
|
FINISHED |
| Object | MILF |
—
|
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: MILF | Statement: [Moms I’d Like to Follow, recasts, MILF]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recasts Context triple: [Moms I’d Like to Follow, recasts, MILF]
-
A.
recastOf
Indicates that one entity is a new or different version, adaptation, or reinterpretation of another, typically replacing or redoing the original in a similar role or context.
-
B.
recast
chosen
Indicates that an entity is assigned a new role or form, replacing a previous assignment or interpretation in a given context.
-
C.
recastIn
Indicates that an entity has been assigned or transformed into a new role, form, or representation, replacing or altering its previous casting or configuration.
-
D.
recites
Indicates that one entity verbally delivers or repeats from memory the words, text, or performance associated with another entity.
-
E.
recastBy
Indicates that an existing role, character, or part has been newly assigned to a different performer or entity than before.
- 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_69f3493323288190a4e88251035fe96e |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6c81cd47c8190b3b8d476327688b8 |
completed | May 3, 2026, 3:59 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f617c08190a70ba880210f908c |
completed | May 3, 2026, 3:41 a.m. |
Created at: May 1, 2026, 1:10 a.m.