Triple
T29055159
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hurro-Urartian |
E735365
|
entity |
| Predicate | consideredBySomeToBeRelatedTo |
P125111
|
FINISHED |
| Object | Northeast Caucasian languages |
—
|
NE NERFINISHED |
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: Northeast Caucasian languages | Statement: [Hurro-Urartian, consideredBySomeToBeRelatedTo, Northeast Caucasian languages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: consideredBySomeToBeRelatedTo Context triple: [Hurro-Urartian, consideredBySomeToBeRelatedTo, Northeast Caucasian languages]
-
A.
mayRelateTo
chosen
Indicates a possible, but not certain, relationship or association between two entities.
-
B.
moreCloselyRelatedTo
Indicates that one entity has a stronger or closer relationship, connection, or similarity to a second entity than to some other reference entity.
-
C.
usedToRelate
Indicates that one entity previously had a relationship or association with another, but that relationship no longer holds in the present.
-
D.
alsoConsidered
Indicates that one item is regarded as an alternative or additional option alongside another in a given context.
-
E.
allyRelation
Indicates a cooperative, supportive relationship in which the entities act as allies toward shared or aligned goals.
- 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_69f077e64b88819094d37bdbca8191b3 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f6645ba71c81908044ade6ab577018 |
completed | May 2, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f663362c008190a22afed262f1e426 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 10:11 a.m.