Triple
T8599782
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Cambrai |
E203644
|
entity |
| Predicate | requiredRansomFor |
P21628
|
FINISHED |
| Object | release of Francis I’s sons |
—
|
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: release of Francis I’s sons | Statement: [Treaty of Cambrai, requiredRansomFor, release of Francis I’s sons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiredRansomFor Context triple: [Treaty of Cambrai, requiredRansomFor, release of Francis I’s sons]
-
A.
ransom
chosen
Indicates demanding payment or concessions in exchange for releasing a person, object, or information held under threat or coercion.
-
B.
collateralRequired
Indicates that a party must provide collateral as a condition or security for an obligation, transaction, or agreement.
-
C.
requiredSurrenderOf
Indicates that one party is obligated to give up or relinquish something to another party.
-
D.
ransomPaid
Indicates that a payment has been made to secure the release of a person, property, or information held under threat or coercion.
-
E.
requiredPledgeFrom
Indicates that one entity mandates or demands a pledge or commitment from another entity as a prerequisite or condition.
- 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_69ca832b56948190ba751cec255308f1 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cc46d7c184819083236c75f9ccc9cf |
completed | March 31, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69cc454eb2908190acf0e4336bc67e7b |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:24 p.m.