Triple
T33887593
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kaan dynasty |
E868670
|
entity |
| Predicate | associatedWithGlyph |
P190013
|
FINISHED |
| Object | snake head emblem glyph |
—
|
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: snake head emblem glyph | Statement: [Kaan dynasty, associatedWithGlyph, snake head emblem glyph]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithGlyph Context triple: [Kaan dynasty, associatedWithGlyph, snake head emblem glyph]
-
A.
associatedGlyphMeaning
Indicates a relationship where a glyph is linked to, or represents, a particular meaning or semantic value.
-
B.
associatedWithCharacterGroup
Indicates that an entity has a connection or affiliation with a particular group of characters.
-
C.
associatedWithText
Indicates that an entity has a contextual or semantic connection to a specific piece of text.
-
D.
associatedWithCharacterFamily
Indicates a relationship where something is linked or connected to a particular character’s family.
-
E.
iconographicallyAssociatedWith
chosen
Indicates that two entities are related through shared or corresponding visual symbols, motifs, or iconographic representations.
- 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_69f34996761c8190864e42f7c9cf215b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037e0953908190b2930b3c06a40129 |
completed | May 12, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_6a0379f6c3308190b954f7810214ceed |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:48 a.m.