Triple

T24557832
Position Surface form Disambiguated ID Type / Status
Subject Treaty of London (1550) E607568 entity
Predicate adjusted P46107 FINISHED
Object territorial claims between England and France 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: territorial claims between England and France | Statement: [Treaty of London (1550), adjusted, territorial claims between England and France]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: adjusted
Context triple: [Treaty of London (1550), adjusted, territorial claims between England and France]
  • A. adjustsFor
    Indicates that one entity modifies, compensates, or accounts for the effects of another entity to achieve a corrected or normalized result.
  • B. updated
    Indicates that an entity has been modified or brought to a more recent state compared to its previous version or status.
  • C. amendedFor chosen
    Indicates that one entity has been modified or revised specifically to address, correct, or accommodate another entity.
  • D. notAdjustedFor
    Indicates that a value, measure, or result has not been modified or corrected to account for certain factors, conditions, or variables.
  • E. adjustmentType
    Indicates the specific kind or category of modification applied to an existing value, state, or configuration within the relationship.
  • 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_69e2c4cae1b88190825e88d5ce8aa61e completed April 17, 2026, 11:39 p.m.
NER Named-entity recognition batch_69f2a8f3fa5481909af50dca4156a22f completed April 30, 2026, 12:57 a.m.
PD Predicate disambiguation batch_69f2a6b99e7c8190ba7e2dc8729a314a completed April 30, 2026, 12:47 a.m.
Created at: April 18, 2026, 2:27 a.m.