Triple
T34416120
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Montgomery |
E883406
|
entity |
| Predicate | overlordshipExtent |
P49097
|
FINISHED |
| Object | most of Wales outside the Marches |
—
|
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: most of Wales outside the Marches | Statement: [Treaty of Montgomery, overlordshipExtent, most of Wales outside the Marches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: overlordshipExtent Context triple: [Treaty of Montgomery, overlordshipExtent, most of Wales outside the Marches]
-
A.
typeOfOverlordship
Indicates a hierarchical relationship in which one entity holds overlordship, or superior controlling authority, over another.
-
B.
overlordDuringReign
Indicates that one entity served as the ruling overlord of another entity during a specified reign period.
-
C.
hasSovereignPowerOver
Indicates that one entity holds ultimate governing authority or supreme ruling power over another entity.
-
D.
territorialExtent
Indicates the geographic area or spatial range over which something extends, applies, or has jurisdiction.
-
E.
areaOfAuthority
chosen
Indicates the domain, region, or scope within which an entity has official power, control, or responsibility.
- 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_69f349c2e3b88190a67834eb5bcffeaf |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71947ad88819082ab9d85dd493b01 |
completed | May 3, 2026, 9:45 a.m. |
| PD | Predicate disambiguation | batch_69f71824431081908d9685d2462ea242 |
completed | May 3, 2026, 9:40 a.m. |
Created at: May 1, 2026, 1:59 a.m.