Triple
T13024496
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kamigamo Shrine |
E326264
|
entity |
| Predicate | hasPriestlyLineage |
P107517
|
FINISHED |
| Object | Kamo priestly lineage |
—
|
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: Kamo priestly lineage | Statement: [Kamigamo Shrine, hasPriestlyLineage, Kamo priestly lineage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPriestlyLineage Context triple: [Kamigamo Shrine, hasPriestlyLineage, Kamo priestly lineage]
-
A.
divineLineage
Indicates that one entity is descended from, or originates from, a divine or god-like being.
-
B.
hasMatrilinealConnection
Indicates a relationship where one entity is connected to another through a line of descent traced exclusively through female ancestors.
-
C.
hasFaithfulOfRite
Indicates that a religious body or authority has adherents who follow a specific liturgical rite.
-
D.
hasOrthodoxSuccession
Indicates that a position, title, or office has been passed down through a continuous, traditionally recognized line of succession.
-
E.
hasRoyalAncestryFrom
Indicates that one entity possesses royal lineage or descent originating from another entity.
- F. None of above. chosen
Provenance (4 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_69d8076cc45c81908123123f43e69266 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97efac71881908a21d70c3c6ce099 |
completed | April 10, 2026, 10:51 p.m. |
| PD | Predicate disambiguation | batch_69d97dc39a0881908119c62e31bf6182 |
completed | April 10, 2026, 10:46 p.m. |
| PDg | Predicate description generation | batch_69d97e3df2288190a7f27d31d248bb7f |
completed | April 10, 2026, 10:48 p.m. |
Created at: April 9, 2026, 8:52 p.m.