Triple
T31315568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Come Back... Be Here (Taylor’s Version) |
E798584
|
entity |
| Predicate | containsEllipsisInTitle |
P145628
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Come Back... Be Here (Taylor’s Version), containsEllipsisInTitle, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsEllipsisInTitle Context triple: [Come Back... Be Here (Taylor’s Version), containsEllipsisInTitle, true]
-
A.
hasEllipsisInTitle
chosen
Indicates that the title of an entity contains an ellipsis (three consecutive dots or a similar omission marker).
-
B.
hasEllipsis
Indicates that one element contains or is associated with an ellipsis (a deliberate omission or trailing-off in text or speech).
-
C.
containsTitle
Indicates that one entity includes or holds another entity’s title as part of its content or metadata.
-
D.
hasAsteriskInTitle
Indicates that the entity’s title contains at least one asterisk character.
-
E.
hasTitleIn
Indicates that an entity holds or is associated with a specific title within a particular context, domain, or language.
- 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_69f224e1932c81908fef14f7b03a10b7 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69ff6fba1a5c8190a660279a6271d785 |
completed | May 9, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69ff6f59388c8190a7d6ab7bc7705bc0 |
completed | May 9, 2026, 5:31 p.m. |
Created at: April 29, 2026, 9:15 p.m.