Triple
T33475023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Valeria (Roman province) |
E857295
|
entity |
| Predicate | hadFrontierType |
P81735
|
FINISHED |
| Object | limes |
—
|
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: limes | Statement: [Valeria (Roman province), hadFrontierType, limes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadFrontierType Context triple: [Valeria (Roman province), hadFrontierType, limes]
-
A.
frontierSystem
Indicates a system that lies at or near the boundary or edge of a defined region, domain, or area of control.
-
B.
wasFrontierRegion
Indicates that a region historically functioned as a frontier area, marking a boundary or border zone between larger political or cultural entities.
-
C.
wasFrontierBetween
Indicates that one entity historically served as the boundary or border region separating two other entities.
-
D.
typeOfFrontierUnit
chosen
Indicates that one unit is classified as a specific type or category of frontier unit in relation to another.
-
E.
hasFrontierRole
Indicates that an entity holds a designated role or function at the frontier or boundary of a system, domain, or organization.
- 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_69f3497472508190b300ebd3fd402367 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e501c1fc819081b14287930e834d |
completed | May 3, 2026, 6:02 a.m. |
| PD | Predicate disambiguation | batch_69f6e3da41948190a4cfe866ce184f73 |
completed | May 3, 2026, 5:57 a.m. |
Created at: May 1, 2026, 1:38 a.m.