Triple
T30096799
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Black Prince |
E764887
|
entity |
| Predicate | intertextualReference |
P52226
|
FINISHED |
| Object | Hamlet |
—
|
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: Hamlet | Statement: [The Black Prince, intertextualReference, Hamlet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intertextualReference Context triple: [The Black Prince, intertextualReference, Hamlet]
-
A.
intertextualRelation
chosen
Indicates a relationship in which one text references, echoes, or otherwise meaningfully connects to another text.
-
B.
coreTextReferenced
Indicates that one text directly cites, mentions, or otherwise refers to another core text as a reference point.
-
C.
alsoRefersTo
Indicates that one term, label, or identifier is used as an alternative designation for the same entity or concept as another.
-
D.
notablyRefersTo
Indicates that one entity makes a particularly significant or noteworthy reference to another entity, beyond a routine or incidental mention.
-
E.
crossReference
Indicates that one entity refers the user to another related entity or source for additional or supporting information.
- 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_69f22474e4288190b5f895fe3974aa92 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd13595c81908719f52c3d37a7e8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: April 29, 2026, 7:07 p.m.