Triple
T4495562
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aaron |
E100685
|
entity |
| Predicate | repentedFor |
P12206
|
FINISHED |
| Object | golden calf incident |
—
|
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: golden calf incident | Statement: [Aaron, repentedFor, golden calf incident]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: repentedFor Context triple: [Aaron, repentedFor, golden calf incident]
-
A.
confessedFor
Indicates that one entity admitted guilt or responsibility on behalf of another entity.
-
B.
confessedTo
Indicates that one entity admitted guilt or revealed the truth about an action, wrongdoing, or secret to another entity.
-
C.
apologizedFor
chosen
Indicates that one entity expressed regret or remorse to another entity specifically about a particular action, event, or wrongdoing.
-
D.
contritionType
Indicates the specific kind or category of contrition (remorse or repentance) associated with an action or state.
-
E.
confessedAs
Indicates that one entity has admitted or acknowledged being or doing something, typically revealing guilt, identity, or involvement in relation 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_69bd43cdf15081909a4fa2585ff63b3e |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd56bde14c819091d42839a46291d0 |
completed | March 20, 2026, 2:16 p.m. |
| PD | Predicate disambiguation | batch_69bd521671688190bc655d25fa77eba2 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1 p.m.