Triple
T32694735
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moms I’d Like to Follow |
E835974
|
entity |
| Predicate | isPlayOn |
P174798
|
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, isPlayOn, MILF]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPlayOn Context triple: [Moms I’d Like to Follow, isPlayOn, MILF]
-
A.
isPlayedUnder
Indicates that an activity, game, or performance occurs while subject to specific rules, conditions, or circumstances defined by another entity.
-
B.
isOn
Indicates that one entity is physically positioned above and in contact with the top surface of another entity.
-
C.
isNormalPlay
Indicates that the play or move occurs under standard, non-exceptional conditions or rules within the given context.
-
D.
isInPlayBy
Indicates that an entity is currently active or participating within a game, scenario, or context as a result of actions taken by a specific agent or player.
-
E.
continuesToPlay
Indicates that an entity persists in engaging in a play activity or game over a period of time, without stopping.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69f6c77500a08190b2bdeca33bd2ac08 |
completed | May 3, 2026, 3:56 a.m. |
Created at: May 1, 2026, 1:10 a.m.