Triple
T29054044
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ironclad Oath |
E735339
|
entity |
| Predicate | graduallyWeakenedBy |
P12615
|
FINISHED |
| Object | amnesty acts |
—
|
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: amnesty acts | Statement: [Ironclad Oath, graduallyWeakenedBy, amnesty acts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: graduallyWeakenedBy Context triple: [Ironclad Oath, graduallyWeakenedBy, amnesty acts]
-
A.
weakenedDuring
chosen
Indicates that an entity’s strength, intensity, or effectiveness is reduced over the course of a specified time period or event.
-
B.
weakerThan
Indicates that one entity has less strength, power, or effectiveness than another entity.
-
C.
aimedToWeaken
Indicates an action or strategy that was intentionally directed toward reducing the strength, influence, or effectiveness of a target.
-
D.
hasWeakness
Indicates that one entity is vulnerable to, or can be adversely affected or defeated by, another entity.
-
E.
graduallyPhasedOutIn
Indicates that something is discontinued or removed in a particular context or period through a slow, step-by-step process rather than all at once.
- 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_69f077e64b88819094d37bdbca8191b3 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f6609061508190ae12005d993e42bc |
completed | May 2, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69f659d297cc8190b2b962ba30a1edb3 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 10:10 a.m.