Triple
T24438296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | the three gods |
E616183
|
entity |
| Predicate | expectsFrom |
P128116
|
FINISHED |
| Object | goodness from Shen Te |
—
|
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: goodness from Shen Te | Statement: [the three gods, expectsFrom, goodness from Shen Te]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expectsFrom Context triple: [the three gods, expectsFrom, goodness from Shen Te]
-
A.
expectsEvent
Indicates that one entity anticipates, awaits, or is scheduled to receive the occurrence of a specific event.
-
B.
expectsInheritanceFrom
Indicates that one entity anticipates or is intended to receive inheritance (such as assets, rights, or properties) from another entity.
-
C.
holderExpectation
chosen
Indicates that one entity has an expectation, belief, or anticipated outcome regarding another entity or situation.
-
D.
setsExpectationsFor
Indicates that one entity defines or communicates standards, requirements, or anticipated outcomes that another entity is expected to meet or follow.
-
E.
expectedValue
Indicates the predicted or average outcome of a variable or event, typically computed as a probability-weighted sum of all possible values.
- 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_69e2d7ec44b081909ccaf1f3bbec0641 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f297881fa08190b82bdc5ebeae96f7 |
completed | April 29, 2026, 11:43 p.m. |
| PD | Predicate disambiguation | batch_69f287d3237c819099559c00f83131d8 |
completed | April 29, 2026, 10:36 p.m. |
Created at: April 18, 2026, 2:16 a.m.