Triple
T8226654
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Classis Pannonica |
E192188
|
entity |
| Predicate | borderOpponents |
P81737
|
FINISHED |
| Object | tribes north of the Danube |
—
|
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: tribes north of the Danube | Statement: [Classis Pannonica, borderOpponents, tribes north of the Danube]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderOpponents Context triple: [Classis Pannonica, borderOpponents, tribes north of the Danube]
-
A.
borderCountrySide
Indicates that one country shares a land border with the side or region of another country.
-
B.
borderStraddling
Indicates that something (such as a feature, structure, or area) extends across and occupies territory on both sides of a border between two regions or jurisdictions.
-
C.
borderedBy
Indicates that one entity shares a common boundary or edge with another entity.
-
D.
borderPoint
Indicates a point that lies on the boundary between two regions or entities.
-
E.
borderDefinedBy
Indicates that the boundary or limit of one entity is determined, shaped, or delineated by another entity.
- F. None of above. chosen
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_69ca82db5b90819085d1ad7c2e27bfcc |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb77fc10f48190b7e241c89885a478 |
completed | March 31, 2026, 7:30 a.m. |
| PD | Predicate disambiguation | batch_69cb36af41e081909dee92b9bc4947f1 |
completed | March 31, 2026, 2:51 a.m. |
| PDg | Predicate description generation | batch_69cb4d9b03108190a6785834f21ff75e |
completed | March 31, 2026, 4:29 a.m. |
Created at: March 30, 2026, 5:46 p.m.