Triple
T837133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Eustace Diamonds |
E18092
|
entity |
| Predicate | notableObjectInPlot |
P7672
|
FINISHED |
| Object | diamond necklace |
—
|
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: diamond necklace | Statement: [The Eustace Diamonds, notableObjectInPlot, diamond necklace]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableObjectInPlot Context triple: [The Eustace Diamonds, notableObjectInPlot, diamond necklace]
-
A.
notableObject
chosen
Indicates that an entity is especially significant, famous, or noteworthy as an object in a given context or domain.
-
B.
plotInvolvement
Indicates that an entity participates in, contributes to, or is affected by the events or storyline of a narrative work.
-
C.
notableObjectOfStudy
Indicates that a subject is a significant or prominent focus of research, analysis, or scholarly attention for another entity.
-
D.
notableElement
Indicates that an entity has a component, feature, or part that is especially significant, prominent, or noteworthy in relation to it.
-
E.
notObservedIn
Indicates that a particular entity, event, or property has not been detected, recorded, or seen within a specified context, dataset, or environment.
- 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_69a49389f44881909a608fb27d89f247 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4abcf69888190b342363978273ae2 |
completed | March 1, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69a4aa7dfc5c8190890c9df485d73a86 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:38 p.m.