Triple
T24237069
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Etaples (1492) |
E601913
|
entity |
| Predicate | pensionAmountApproximate |
P9121
|
FINISHED |
| Object | £5,000 per year |
—
|
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: £5,000 per year | Statement: [Treaty of Etaples (1492), pensionAmountApproximate, £5,000 per year]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pensionAmountApproximate Context triple: [Treaty of Etaples (1492), pensionAmountApproximate, £5,000 per year]
-
A.
pensionAmount
chosen
Indicates the specific monetary value of a pension that is assigned to or received by an entity.
-
B.
pensionEligibility
Indicates that an entity qualifies to receive pension benefits under specified rules or conditions.
-
C.
receivesPensionFrom
Indicates that one entity is the source or provider of a pension that another entity receives.
-
D.
plannedRetirement
Indicates that an entity has scheduled or intends to end its active role or service at a specified future time.
-
E.
pensionIssue
Indicates that an entity is involved in the granting, receiving, managing, or disputing of a pension or retirement-benefit payment.
- 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_69e29538aafc8190a2386fdebbd1393b |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f28a9c5c3081909cfddc8d29121817 |
completed | April 29, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69f1c448abec8190b87cbf9ed419a309 |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:02 a.m.