Triple
T36091925
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | We Know Where You Fucking Live |
E1043940
|
entity |
| Predicate | hasTitleCasing |
P196021
|
FINISHED |
| Object | We Know Where You F***ing Live |
—
|
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: We Know Where You F***ing Live | Statement: [We Know Where You Fucking Live, hasTitleCasing, We Know Where You F***ing Live]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTitleCasing Context triple: [We Know Where You Fucking Live, hasTitleCasing, We Know Where You F***ing Live]
-
A.
hasNameInCaseTitle
Indicates that a legal case’s title explicitly contains the name of the referenced entity.
-
B.
hasTitleLetter
Indicates that an entity possesses a specific letter or character within its title.
-
C.
hasTitleOf
Indicates that one entity holds, bears, or is designated by the official title, name, or rank specified by another entity.
-
D.
hasTitleIn
Indicates that an entity holds or is associated with a specific title within a particular context, domain, or language.
-
E.
hasTitleInName
Indicates that an entity’s name explicitly includes a specified title as part of it.
- 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_69f76e32d60c8190ba781ffaaab4aa3d |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fe00dad1708190b6522476bebb43af |
completed | May 8, 2026, 3:27 p.m. |
| PD | Predicate disambiguation | batch_69fdfc3717f48190bb50ac2919c8ef95 |
completed | May 8, 2026, 3:07 p.m. |
| PDg | Predicate description generation | batch_69fe00d8d8248190a63c12aa2c2f7c0c |
completed | May 8, 2026, 3:27 p.m. |
Created at: May 3, 2026, 4:08 p.m.