Triple
T35674436
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cetingrad |
E1030814
|
entity |
| Predicate | hasBorderlandHistory |
P93966
|
FINISHED |
| Object | Military Frontier |
—
|
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: Military Frontier | Statement: [Cetingrad, hasBorderlandHistory, Military Frontier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBorderlandHistory Context triple: [Cetingrad, hasBorderlandHistory, Military Frontier]
-
A.
hasHistoricTerritory
Indicates that an entity possesses or claims a territory that it historically occupied, controlled, or was associated with in the past.
-
B.
hasHistoricalTerritoryNear
Indicates that an entity historically controlled or claimed territory in geographic proximity to another specified location or region.
-
C.
hasSharedBorderHistoryWith
chosen
Indicates that two entities have a history of sharing a common border or boundary at some point in time.
-
D.
hasHistoricalRegionOnSouthernBoundary
Indicates that an entity’s southern boundary is adjacent to or defined by a specific historical region.
-
E.
borderHistory
Indicates the historical changes, events, or status of borders between entities over time.
- 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_69f76e0acfc0819082c8495c2210ce73 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fdec5ffe088190ac5505f26c6cff18 |
completed | May 8, 2026, 2 p.m. |
| PD | Predicate disambiguation | batch_69fdeae15f1c81908fc63fbc1b028d2e |
completed | May 8, 2026, 1:53 p.m. |
Created at: May 3, 2026, 4:05 p.m.