Triple
T28757769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Semitic |
E731717
|
entity |
| Predicate | typologicalContact |
P22730
|
FINISHED |
| Object | Sumerian |
—
|
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: Sumerian | Statement: [East Semitic, typologicalContact, Sumerian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typologicalContact Context triple: [East Semitic, typologicalContact, Sumerian]
-
A.
typologicalGroup
Indicates that entities are classified together based on shared structural or typological characteristics.
-
B.
hasContactType
Indicates the specific kind or category of contact relationship that exists between two entities.
-
C.
contactWith
Indicates that two entities are in direct or indirect physical or communicative interaction or touch with each other.
-
D.
languageContactWith
chosen
Indicates a relationship where two or more languages come into contact through their speakers, leading to interaction and potential mutual influence.
-
E.
allyType
Indicates that one entity is classified as a specific type or category of ally in relation to 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_69f043ed68a881909e858a06bab7a247 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f658ee40088190b71e1219407690d0 |
completed | May 2, 2026, 8:05 p.m. |
| PD | Predicate disambiguation | batch_69f65760fd3081908ffe014a5e2bf069 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 6:10 a.m.