Triple
T34653805
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tripartite Indenture of 1405 |
E889915
|
entity |
| Predicate | regionToBeControlledByPercy |
P82949
|
FINISHED |
| Object | northern England |
—
|
NE NERFINISHED |
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: northern England | Statement: [Tripartite Indenture of 1405, regionToBeControlledByPercy, northern England]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionToBeControlledByPercy Context triple: [Tripartite Indenture of 1405, regionToBeControlledByPercy, northern England]
-
A.
controlsRegion
chosen
Indicates that one entity has authoritative power or governing influence over a specified geographic or administrative region.
-
B.
occupiedRegion
Indicates that an entity has taken control of and is currently holding a specific geographic area or region.
-
C.
rangeControlledBy
Indicates that the extent or scope of something is regulated, limited, or determined by another entity.
-
D.
regionAtStake
Indicates that a specific geographic or political area is the subject of contention, risk, or negotiation within a given situation or interaction.
-
E.
regulatesArea
Indicates that one entity exercises control or governance over the spatial extent, scope, or domain of another entity.
- 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_69f349d906bc8190b2efd9eff237d94b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff8aff48988190a48a440de8238ef9 |
completed | May 9, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69ff8a780404819082f48ceb21e7fe11 |
completed | May 9, 2026, 7:26 p.m. |
Created at: May 1, 2026, 2:04 a.m.