Triple
T1846727
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Colchis |
E41299
|
entity |
| Predicate | cultureLinkedTo |
P958
|
FINISHED |
| Object | ancient Georgian tribes |
—
|
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: ancient Georgian tribes | Statement: [Colchis, cultureLinkedTo, ancient Georgian tribes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cultureLinkedTo Context triple: [Colchis, cultureLinkedTo, ancient Georgian tribes]
-
A.
hasCulturalSignificanceFor
chosen
Indicates that something holds particular cultural meaning, value, or importance for a specified group or community.
-
B.
associatedCult
Indicates that an entity is connected or linked to a particular cult, typically through membership, affiliation, or influence.
-
C.
cultureDepicted
Indicates that one entity portrays, represents, or is associated with the culture of another entity.
-
D.
hasCulturalWorkNamedAfterIt
Indicates that something has a cultural work (such as a book, film, song, or artwork) that is named after it.
-
E.
culturalCategory
Indicates that one entity classifies or groups another entity according to a particular culture, tradition, or culturally defined type.
- 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_69a88648cd44819093303206d96d76ad |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb32d35508190bf1c487dffbecaf0 |
completed | March 7, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69abafdca6d8819083c66f3a29fd9fd1 |
completed | March 7, 2026, 4:55 a.m. |
Created at: March 4, 2026, 7:33 p.m.