Triple
T9338915
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liutprandian line |
E224714
|
entity |
| Predicate | dynasticPowerBase |
P62167
|
FINISHED |
| Object | northern Italy |
—
|
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: northern Italy | Statement: [Liutprandian line, dynasticPowerBase, northern Italy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dynasticPowerBase Context triple: [Liutprandian line, dynasticPowerBase, northern Italy]
-
A.
dynasticDomain
Indicates that a domain, territory, or sphere of influence is under the control or authority of a particular dynasty or ruling family.
-
B.
dynasticState
Indicates a relationship where a state or political entity is ruled or defined by a hereditary dynasty or ruling family.
-
C.
dynasticSphere
chosen
Indicates a sphere of influence or control defined by dynastic ties, where power, authority, or allegiance is organized around a particular ruling family or lineage.
-
D.
dynasticType
Indicates the specific kind or category of dynastic relationship or succession pattern that applies between ruling entities or lineages.
-
E.
dynasticOrigin
Indicates the historical dynasty or ruling family from which an entity originates or descends.
- 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_69ca84286fcc81909f6e7fd7a7e862a2 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd4bace8488190a18c54e03be8410c |
completed | April 1, 2026, 4:45 p.m. |
| PD | Predicate disambiguation | batch_69cc7a66aef08190b8d668cff5b04f5f |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:40 p.m.