Triple
T22575962
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Proud |
E544394
|
entity |
| Predicate | mayImply |
P72358
|
FINISHED |
| Object | moral rigidity |
—
|
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: moral rigidity | Statement: [The Proud, mayImply, moral rigidity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayImply Context triple: [The Proud, mayImply, moral rigidity]
-
A.
mayEntail
chosen
Indicates that one statement or condition can logically lead to or imply the truth of another, without guaranteeing it.
-
B.
mayResultIn
Indicates that one entity has the potential to cause, lead to, or bring about another entity or outcome, without guaranteeing that it will occur.
-
C.
implies
Indicates that the truth of one statement guarantees or leads logically to the truth of another statement.
-
D.
hasImplicationsFor
Indicates that one entity’s state, action, or condition leads to consequences, effects, or relevance for another entity.
-
E.
mayGrant
Indicates that one entity has the authority or permission to confer, assign, or bestow a right, privilege, or resource to 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_69e11e30d05481909df915354c89f0d6 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f15fecf1c8819091a05f2a1b93ca8a |
completed | April 29, 2026, 1:33 a.m. |
| PD | Predicate disambiguation | batch_69ee626e6bb08190ada4dd8b48cc0c43 |
completed | April 26, 2026, 7:07 p.m. |
Created at: April 16, 2026, 8:53 p.m.