Triple
T35243736
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lord of Villoria |
E1017600
|
entity |
| Predicate | hasTerritorialLordship |
P182343
|
FINISHED |
| Object | Villoria |
—
|
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: Villoria | Statement: [Lord of Villoria, hasTerritorialLordship, Villoria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTerritorialLordship Context triple: [Lord of Villoria, hasTerritorialLordship, Villoria]
-
A.
lordshipHeldIn
chosen
Indicates that an entity holds or exercises lordship, authority, or feudal control within a specified place or territorial jurisdiction.
-
B.
hasTerritorialSee
Indicates that a religious or ecclesiastical jurisdiction is associated with a specific territorial see (a defined geographic seat of authority).
-
C.
hasTerritorialPossession
Indicates that one entity holds ownership, control, or legal rights over a specific territory or geographic area.
-
D.
lordshipType
Indicates the specific kind or category of lordship relationship that exists between one entity and another.
-
E.
hasSovereignPowerOver
Indicates that one entity holds ultimate governing authority or supreme ruling power over 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_69f76de235048190b990070c23c51b6b |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fe5ec9028081909ae3d6fbe2f4cbbc |
completed | May 8, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69fe5e1d715881909fc516fafc707644 |
completed | May 8, 2026, 10:05 p.m. |
Created at: May 3, 2026, 4:02 p.m.