Triple
T15169279
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gurieli dynasty |
E362441
|
entity |
| Predicate | hereditaryRule |
P31750
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Gurieli dynasty, hereditaryRule, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hereditaryRule Context triple: [Gurieli dynasty, hereditaryRule, yes]
-
A.
hereditaryJurisdiction
Indicates that an entity holds legal authority or judicial power that is passed down through inheritance within a family or lineage.
-
B.
heritageSuccessor
Indicates that one entity is the successor or inheritor of another in terms of heritage, lineage, or cultural tradition.
-
C.
hasInheritanceRule
Indicates that a specific rule or policy governs how rights, properties, or attributes are passed from one entity to another.
-
D.
hasHereditaryChief
chosen
Indicates that an entity is led or governed by a chief whose position is inherited through family lineage.
-
E.
assumedRuleOf
Indicates that one entity is presumed or taken to hold authoritative control, governance, or dominion over another entity, typically without definitive confirmation.
- 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_69d85a087b7c81908baa94a53dac8d68 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0064dba588190a4341775b472a6d3 |
completed | April 15, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69deb9779acc81908ed2dad382c42dca |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:08 a.m.