Triple
T32908797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brigetio |
E841815
|
entity |
| Predicate | onFrontierWith |
P165704
|
FINISHED |
| Object | Barbaricum |
—
|
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: Barbaricum | Statement: [Brigetio, onFrontierWith, Barbaricum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: onFrontierWith Context triple: [Brigetio, onFrontierWith, Barbaricum]
-
A.
frontierWith
chosen
Indicates that two regions or territories share a common boundary or border, especially one marking the edge of settled or controlled area.
-
B.
hasFrontierRole
Indicates that an entity holds a designated role or function at the frontier or boundary of a system, domain, or organization.
-
C.
frontierSystem
Indicates a system that lies at or near the boundary or edge of a defined region, domain, or area of control.
-
D.
frontOf
Indicates that one entity is positioned directly before another along a primary viewing or movement direction.
-
E.
FrontierStatus
Indicates the status or condition of something in relation to a boundary, edge, or frontier context (such as being at, beyond, or within that frontier).
- 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_69f34946a5208190bbd79f0fec4323bd |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d0d46aec819091edf97324d793ac |
completed | May 3, 2026, 4:36 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe5f93c8190995c53dbbe380a32 |
completed | May 3, 2026, 4:32 a.m. |
Created at: May 1, 2026, 1:19 a.m.