Triple
T36556685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Westfold |
E901714
|
entity |
| Predicate | governedRegionType |
P21121
|
FINISHED |
| Object | mark of Rohan |
E927791
|
NE 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: mark of Rohan | Statement: [The Westfold, governedRegionType, mark of Rohan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governedRegionType Context triple: [The Westfold, governedRegionType, mark of Rohan]
-
A.
governsTerritoryType
chosen
Indicates that an authority or governing body exercises official control or administration over a specified type of territory.
-
B.
governedTerritory
Indicates that one entity exercises political authority or control over another entity or geographic area as its governing power.
-
C.
governedTerritoryCharacteristic
Indicates that a governing entity is associated with a specific characteristic or attribute of the territory it governs.
-
D.
governedTerritoryWith
Indicates that one entity exercised governing authority or control over a specified territory, region, or domain in association with another entity.
-
E.
governedIn
Indicates that one entity exercised governing authority or administrative control within a specified place or jurisdiction.
- F. None of above.
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_69f76e634e9481908c9ba1b87ab87c26 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a02fc3890a881908b69b0f2d7cc1ce1 |
completed | May 12, 2026, 10:08 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a39e6f034fc8190af0ebae6ade6f48b |
completed | June 23, 2026, 1:52 a.m. |
| PD | Predicate disambiguation | batch_6a02fb98438c8190938896c00216b9ec |
completed | May 12, 2026, 10:06 a.m. |
Created at: May 3, 2026, 4:11 p.m.