Triple
T33303785
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Love Lies Bleeding |
E852657
|
entity |
| Predicate | titleCharacterPresent |
P12208
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Love Lies Bleeding, titleCharacterPresent, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleCharacterPresent Context triple: [Love Lies Bleeding, titleCharacterPresent, yes]
-
A.
titleCharacterString
Indicates that one entity is the textual string representing the title associated with another entity.
-
B.
titleCharacterState
Indicates the state or condition a character is in within the context of a specific title or work.
-
C.
titleCharacterLocation
Indicates the location or setting associated with the main character referenced in the title.
-
D.
characterIn
chosen
Indicates that an entity appears as a character within a specified work, story, or narrative.
-
E.
titleCharacterNamedAfter
Indicates that a work’s title character is named after, or shares their name with, another specific entity.
- 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_69f34966ed4c81908dc9dda82d8c7fe3 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fef2db323c8190821bda53f22a42be |
completed | May 9, 2026, 8:39 a.m. |
| PD | Predicate disambiguation | batch_69fef21d63c88190abf6a99b59b3c655 |
completed | May 9, 2026, 8:36 a.m. |
Created at: May 1, 2026, 1:33 a.m.