Triple
T934856
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Esther |
E20171
|
entity |
| Predicate | hasAddition |
P4097
|
FINISHED |
| Object | Greek additions to Esther in the Septuagint |
—
|
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: Greek additions to Esther in the Septuagint | Statement: [Esther, hasAddition, Greek additions to Esther in the Septuagint]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAddition Context triple: [Esther, hasAddition, Greek additions to Esther in the Septuagint]
-
A.
addedTo
chosen
Indicates that one entity has been included or incorporated into another entity, typically as a new component, member, or element.
-
B.
isAdditiveFor
Indicates that one entity can be combined with another in a way that their effects or quantities sum together to produce a cumulative result.
-
C.
hasCreation
Indicates a relationship where one entity is the creator or originator of another entity.
-
D.
hasSupplement
Indicates that one entity provides or is associated with an additional supporting or enhancing item, resource, or component for another entity.
-
E.
hasUpgrade
Indicates that one entity possesses, includes, or is associated with an improved or enhanced version of another 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_69a493af3dc48190adb7263e6e445ea1 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b363ea5c819098ec1d87f785bad4 |
completed | March 1, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69a4b29b245c8190b143f28b77fede3c |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:40 p.m.