Triple
T316163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Laz people |
E7710
|
entity |
| Predicate | ethnogenesis |
P1823
|
FINISHED |
| Object | ancient Colchian 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 Colchian tribes | Statement: [Laz people, ethnogenesis, ancient Colchian tribes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ethnogenesis Context triple: [Laz people, ethnogenesis, ancient Colchian tribes]
-
A.
ethnonym
Indicates that one entity is the name of an ethnic group used to refer to the people associated with another entity.
-
B.
ethnicOrigin
Indicates the relationship where an entity is associated with a particular ethnic group or ancestry.
-
C.
ethnoreligiousIdentity
Indicates a relationship where an entity is characterized by a combined ethnic and religious group identity.
-
D.
etymology
Indicates the historical origin and development of a word or term, including its source language and form.
-
E.
historicalOrigin
chosen
Indicates the relationship by which one entity serves as the source, origin, or starting point in history for another entity.
- 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_69a2e7e7af7881908890039d6be4e9b8 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ea6462148190825acc57f6d2adaf |
completed | Feb. 28, 2026, 1:15 p.m. |
| PD | Predicate disambiguation | batch_69a2e943f12c8190883854aeed974260 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.