Triple
T4351456
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apology Resolution (U.S. Public Law 103-150) |
E98034
|
entity |
| Predicate | typeOfApology |
P55701
|
FINISHED |
| Object | symbolic apology |
—
|
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: symbolic apology | Statement: [Apology Resolution (U.S. Public Law 103-150), typeOfApology, symbolic apology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfApology Context triple: [Apology Resolution (U.S. Public Law 103-150), typeOfApology, symbolic apology]
-
A.
apologyIssued
Indicates that one entity has expressed regret or remorse to another entity for a perceived wrong, mistake, or offense.
-
B.
apologizedFor
Indicates that one entity expressed regret or remorse to another entity specifically about a particular action, event, or wrongdoing.
-
C.
apologeticMethod
Indicates the manner or approach by which an apology is expressed or delivered from one entity to another.
-
D.
contritionType
Indicates the specific kind or category of contrition (remorse or repentance) associated with an action or state.
-
E.
apologyDate
Indicates the date on which an apology was made or formally recorded.
- F. None of above. chosen
Provenance (4 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_69b3454965f881908c41190bb22f0e4b |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b351a99788819080b13a20124e49a0 |
completed | March 12, 2026, 11:52 p.m. |
| PD | Predicate disambiguation | batch_69b34f51ed7c8190b7bf5f44b56b730d |
completed | March 12, 2026, 11:42 p.m. |
| PDg | Predicate description generation | batch_69b34ff654308190b9717526120d80d3 |
completed | March 12, 2026, 11:44 p.m. |
Created at: March 12, 2026, 11:15 p.m.