Triple
T24967622
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lordship of Clun |
E624791
|
entity |
| Predicate | typeOfBorderLordship |
P166563
|
FINISHED |
| Object | semi-autonomous marcher territory |
—
|
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: semi-autonomous marcher territory | Statement: [Lordship of Clun, typeOfBorderLordship, semi-autonomous marcher territory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfBorderLordship Context triple: [Lordship of Clun, typeOfBorderLordship, semi-autonomous marcher territory]
-
A.
borderLord
Indicates that one entity serves as the feudal or territorial lord presiding over a border or frontier region associated with another entity.
-
B.
typeOfOverlordship
Indicates a hierarchical relationship in which one entity holds overlordship, or superior controlling authority, over another.
-
C.
borderingUnitType
Indicates that one unit is adjacent to another unit of a specified type along a shared boundary.
-
D.
countryBorderType
Indicates the type or nature of the border relationship that exists between two countries.
-
E.
hasBorderTownRole
Indicates that an entity serves in an official capacity or role specifically related to a town located on or near a border.
- F. None of above. chosen
Provenance (4 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_69e2ff24512481908e9a72315b8d0354 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f662a29b3881909957a7e3b986653c |
completed | May 2, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69f660eea4648190b0d5e24293607813 |
completed | May 2, 2026, 8:39 p.m. |
| PDg | Predicate description generation | batch_69f661b47d088190934f63884a203261 |
completed | May 2, 2026, 8:42 p.m. |
Created at: April 18, 2026, 6 a.m.