Triple
T28077105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I Poke Her Face |
E709572
|
entity |
| Predicate | usedAsWorkingTitleFor |
P85265
|
FINISHED |
| Object | Make Her Say |
—
|
NE NERFINISHED |
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: Make Her Say | Statement: [I Poke Her Face, usedAsWorkingTitleFor, Make Her Say]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsWorkingTitleFor Context triple: [I Poke Her Face, usedAsWorkingTitleFor, Make Her Say]
-
A.
usedAsWorkingTitleDuring
Indicates that one title temporarily served as the working or provisional title of a work during a specified time period.
-
B.
usedAsTitleOn
Indicates that something functions as a title applied to or displayed on a particular entity.
-
C.
usedAsTitleUntil
Indicates that a particular title was held or used by an entity up to (and including or until) a specified end time.
-
D.
usedTitleIn
Indicates that one entity employed or referenced another entity as a title in some context.
-
E.
alternateWorkingTitle
chosen
Indicates that one title serves as an alternative working title for the same work or project as another title.
- 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_69ef9b6f8078819098b741274cd1a2ee |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f7516d5b4081908588a6feb541f355 |
completed | May 3, 2026, 1:45 p.m. |
| PD | Predicate disambiguation | batch_69f74d40ebb081909daf60623e38f41d |
completed | May 3, 2026, 1:27 p.m. |
Created at: April 27, 2026, 8:49 p.m.