Triple
T31580058
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Karluk territories |
E805796
|
entity |
| Predicate | partlyOverlappedWith |
P1867
|
FINISHED |
| Object | Karakhanid realm |
E170105
|
NE 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: Karakhanid realm | Statement: [Karluk territories, partlyOverlappedWith, Karakhanid realm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partlyOverlappedWith Context triple: [Karluk territories, partlyOverlappedWith, Karakhanid realm]
-
A.
partiallyOn
Indicates that one entity rests or extends over another such that only a portion of its area, volume, or length is supported or in contact.
-
B.
overlapsWith
chosen
Indicates that two entities share a common part or region in space, time, or extent, but neither is completely contained within the other.
-
C.
partiallyEnclosed
Indicates that one entity surrounds or covers another entity to some extent, but not completely.
-
D.
partlyCoveredBy
Indicates that one entity is covered or overlapped by another entity, but only to a partial extent rather than completely.
-
E.
isPartially
Indicates that one entity is included within another to some extent, but not completely or fully.
- F. None of above.
Provenance (4 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_69f348d3a86c8190a3e5e539a4dd125f |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a8083a488190918c52744b210af5 |
completed | May 3, 2026, 1:42 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2b79c555d08190ad7fa40f7989c982 |
completed | June 12, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69f6a75656e081908739ed9e2f600e42 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 30, 2026, 10:22 p.m.