Triple
T952151
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Richard I of England |
E20544
|
entity |
| Predicate | ransom |
P21628
|
FINISHED |
| Object | large ransom paid for release in 1194 |
—
|
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: large ransom paid for release in 1194 | Statement: [Richard I of England, ransom, large ransom paid for release in 1194]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ransom Context triple: [Richard I of England, ransom, large ransom paid for release in 1194]
-
A.
plea
Indicates that a defendant formally states their response (such as guilty, not guilty, or no contest) to criminal charges in a legal proceeding.
-
B.
restriction
Indicates a limiting condition or rule that constrains or controls what an entity can do, use, or access in relation to another entity or context.
-
C.
sacrifice
Indicates giving up something of value, often for the benefit, protection, or advantage of another entity or goal.
-
D.
traction
Indicates the degree to which one entity’s movement or influence effectively grips, pulls, or gains momentum relative to another entity or medium.
-
E.
lootedBy
Indicates that something has been forcibly taken or plundered by a specified agent or group.
- 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_69a493b0f2fc81908cd227480a5356a1 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b3d757d08190a475cf47febd05ae |
completed | March 1, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69a4b2a045308190ab94f3adab40db8d |
completed | March 1, 2026, 9:41 p.m. |
| PDg | Predicate description generation | batch_69a4b30efd2c8190b780a6dee086d0aa |
completed | March 1, 2026, 9:43 p.m. |
Created at: March 1, 2026, 7:40 p.m.