Triple
T34785634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | the Guided One |
E1002796
|
entity |
| Predicate | linkedToExpectation |
P128116
|
FINISHED |
| Object | universal justice |
—
|
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: universal justice | Statement: [the Guided One, linkedToExpectation, universal justice]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linkedToExpectation Context triple: [the Guided One, linkedToExpectation, universal justice]
-
A.
holderExpectation
chosen
Indicates that one entity has an expectation, belief, or anticipated outcome regarding another entity or situation.
-
B.
setsExpectationsFor
Indicates that one entity defines or communicates standards, requirements, or anticipated outcomes that another entity is expected to meet or follow.
-
C.
expectsEvent
Indicates that one entity anticipates, awaits, or is scheduled to receive the occurrence of a specific event.
-
D.
expectedValue
Indicates the predicted or average outcome of a variable or event, typically computed as a probability-weighted sum of all possible values.
-
E.
expectedBy
Indicates that one entity is anticipated, required, or relied upon by another as part of a plan, obligation, or dependency.
- 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_69f76db47d408190a24fc7164439ea2d |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fe5d58c3e48190910aa3c23485e2c4 |
completed | May 8, 2026, 10:02 p.m. |
| PD | Predicate disambiguation | batch_69fe5c92090c8190bcfa412c0a3619df |
completed | May 8, 2026, 9:58 p.m. |
Created at: May 3, 2026, 3:59 p.m.