Triple
T7003793
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Brétigny |
E162399
|
entity |
| Predicate | approximateRansomAmount |
P21628
|
FINISHED |
| Object | 3,000,000 écus |
—
|
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: 3,000,000 écus | Statement: [Treaty of Brétigny, approximateRansomAmount, 3,000,000 écus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateRansomAmount Context triple: [Treaty of Brétigny, approximateRansomAmount, 3,000,000 écus]
-
A.
estimatedCost
Indicates the predicted or calculated monetary amount expected to be required for something, such as a project, item, or action.
-
B.
ransom
chosen
Indicates demanding payment or concessions in exchange for releasing a person, object, or information held under threat or coercion.
-
C.
approximateNumberAwarded
Indicates the estimated quantity of awards or recognitions given in a particular context or event.
-
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.
economicDamageApprox
Indicates that one entity has caused or is associated with an estimated or approximate amount of economic damage to another entity or system.
- 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_69c6885928148190ae31909fbb5e9849 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6dc12af788190b3d06ffc46568410 |
completed | March 27, 2026, 7:35 p.m. |
| PD | Predicate disambiguation | batch_69c6d7c67c94819084fdcf0398606027 |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:33 p.m.