Triple
T27852472
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Karlani confederation |
E703992
|
entity |
| Predicate | borderlandsRole |
P82254
|
FINISHED |
| Object | inhabits Durand Line frontier |
—
|
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: inhabits Durand Line frontier | Statement: [Karlani confederation, borderlandsRole, inhabits Durand Line frontier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderlandsRole Context triple: [Karlani confederation, borderlandsRole, inhabits Durand Line frontier]
-
A.
borderlandsIdentity
chosen
Indicates a complex, hybrid sense of self that emerges in the cultural, social, or geographic margins where different groups, norms, or territories meet and overlap.
-
B.
loreRole
Indicates the specific narrative or canonical function an entity fulfills within a fictional or mythological lore.
-
C.
roleAtLarianStudios
Indicates that an entity holds or held a specific role or position at Larian Studios.
-
D.
roleInGameplay
Indicates the specific function or responsibility an entity has within the context of gameplay or game mechanics.
-
E.
questRole
Indicates the specific function or part an entity plays within a quest or mission.
- 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_69ef840e614c8190a88cf9638c14a265 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69fd19f791f48190bbb6f6047f9ddc59 |
completed | May 7, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69fd0df365948190bc9bfc7ffd46acd8 |
completed | May 7, 2026, 10:10 p.m. |
Created at: April 27, 2026, 6:11 p.m.