Triple
T35343487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lord of Villoria and its land |
E1020671
|
entity |
| Predicate | territorialLordshipOf |
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 and its land, territorialLordshipOf, Villoria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: territorialLordshipOf Context triple: [Lord of Villoria and its land, territorialLordshipOf, Villoria]
-
A.
lordshipType
Indicates the specific kind or category of lordship relationship that exists between one entity and another.
-
B.
lordshipHeldIn
chosen
Indicates that an entity holds or exercises lordship, authority, or feudal control within a specified place or territorial jurisdiction.
-
C.
formerFiefOf
Indicates that a territory or domain was previously under the control or jurisdiction of a specified lord, ruler, or political entity as a fief.
-
D.
lordshipCreated
Indicates that a lordship was formally established or brought into existence.
-
E.
grantedFiefOf
Indicates that one party has been formally given control or ownership of a fief (landed estate) by another authority.
- 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_69f76debb4e08190be52d89b8af2392d |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f79da9f80c8190b0afd8509f28747b |
completed | May 3, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69f79617d40481909ba372f94209c08b |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:03 p.m.