Triple
T34852687
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | medieval Vicenza |
E1004641
|
entity |
| Predicate | hadRulingPower |
P23177
|
FINISHED |
| Object | local feudal nobility |
—
|
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: local feudal nobility | Statement: [medieval Vicenza, hadRulingPower, local feudal nobility]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadRulingPower Context triple: [medieval Vicenza, hadRulingPower, local feudal nobility]
-
A.
hasRulingPeople
Indicates that a group or entity serves as the governing or ruling authority over another entity.
-
B.
hadExecutivePowerIn
chosen
Indicates that an entity held executive authority or governing power within a specified organization, institution, or jurisdiction during a certain period.
-
C.
ruledUnderPolity
Indicates that an entity exercised rule or governance while being subordinate to, or within the authority framework of, a particular polity.
-
D.
ruledOnBy
Indicates that a decision, case, or matter has been formally decided or adjudicated by a specific authority or decision-maker.
-
E.
rulerOf
Indicates that one entity holds governing authority or sovereignty over another entity, such as a person ruling a country or territory.
- 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_69f76dba76f0819090643cba102c41ec |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7886be6d8819095ec62e4f2cee858 |
completed | May 3, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69f7841440f48190b4346c08855951d2 |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4 p.m.