Triple
T6509845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seko languages |
E150098
|
entity |
| Predicate | areRelated |
P37
|
FINISHED |
| Object | each other |
—
|
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: each other | Statement: [Seko languages, areRelated, each other]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: areRelated Context triple: [Seko languages, areRelated, each other]
-
A.
relatedTo
chosen
Indicates a general, non-specific relationship or association exists between two entities.
-
B.
relatedType
Indicates that one entity is connected to another through a specified type or category of relationship.
-
C.
laterRelationWith
Indicates that one entity stands in a temporal relationship to another such that it occurs or exists at a later time than the other.
-
D.
relatedToProduct
Indicates a general association or connection between an entity and a specific product, without specifying the exact nature of that relationship.
-
E.
alsoRefersTo
Indicates that one term, label, or identifier is used as an alternative designation for the same entity or concept as another.
- 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_69c687ef291081909d437f035eef1cda |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c69f398f10819096342f3646cefcc2 |
completed | March 27, 2026, 3:16 p.m. |
| PD | Predicate disambiguation | batch_69c68ab98c78819081743e614df04e1d |
completed | March 27, 2026, 1:48 p.m. |
Created at: March 27, 2026, 1:43 p.m.