Triple
T24780167
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wakefield manor |
E619972
|
entity |
| Predicate | centerOfLordship |
P115353
|
FINISHED |
| Object | Sandal Castle |
—
|
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: Sandal Castle | Statement: [Wakefield manor, centerOfLordship, Sandal Castle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centerOfLordship Context triple: [Wakefield manor, centerOfLordship, Sandal Castle]
-
A.
feudalCenter
Indicates that a location serves as the primary seat of authority, administration, or power within a feudal system.
-
B.
centralCeremonyLocation
Indicates the place that serves as the primary or focal site where a ceremony is held.
-
C.
administrativeCenterForEmpire
Indicates that a location served as the main administrative center or capital for a particular empire.
-
D.
seatOfLiege
chosen
Indicates that a location serves as the primary seat or base of authority for a particular liege or ruling lord.
-
E.
chiefdom
Indicates a hierarchical political relationship in which one central authority (a chief) holds primary power over a group or territory and its subordinate members or communities.
- 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_69e2fabdbe8c8190adbb9434b8636cad |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f497bc12b881908fe3386c66252bf6 |
completed | May 1, 2026, 12:08 p.m. |
| PD | Predicate disambiguation | batch_69f49366e8d08190adb4b71fe3a14683 |
completed | May 1, 2026, 11:49 a.m. |
Created at: April 18, 2026, 4:44 a.m.