Triple
T22536849
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Legacy |
E557176
|
entity |
| Predicate | notableLineTopic |
P103532
|
FINISHED |
| Object | will and testament imagery |
—
|
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: will and testament imagery | Statement: [Legacy, notableLineTopic, will and testament imagery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableLineTopic Context triple: [Legacy, notableLineTopic, will and testament imagery]
-
A.
notableArticleTopic
Indicates that an article is notably about, focused on, or significantly discusses a particular topic.
-
B.
notableEpisodeTopics
Indicates that there is a notable or significant topic discussed in a particular episode.
-
C.
notableStorySubject
chosen
Indicates that the subject is a prominent or central topic, character, or element within a particular story or narrative.
-
D.
subjectNotableFor
Indicates that the subject is especially recognized or distinguished for a particular attribute, achievement, role, or characteristic.
-
E.
notableTitleOnTheLine
Indicates that a significant or prestigious title is at stake or being contested in the associated event or context.
- 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_69e11e57483c8190b0887c4f8ff26446 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15edbd1ec81908ef26b9e442d1921 |
completed | April 29, 2026, 1:29 a.m. |
| PD | Predicate disambiguation | batch_69e898c864148190a3f5feec7967d49c |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:51 p.m.