Triple
T30138831
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Legio VII Claudia |
E766070
|
entity |
| Predicate | stationedOnFrontier |
P88394
|
FINISHED |
| Object | Danube 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: Danube frontier | Statement: [Legio VII Claudia, stationedOnFrontier, Danube frontier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stationedOnFrontier Context triple: [Legio VII Claudia, stationedOnFrontier, Danube frontier]
-
A.
frontierSystem
Indicates a system that lies at or near the boundary or edge of a defined region, domain, or area of control.
-
B.
stationedOn
chosen
Indicates that an entity is assigned to remain at a specific location, platform, or vehicle for duty or operational purposes.
-
C.
wasFrontierRegion
Indicates that a region historically functioned as a frontier area, marking a boundary or border zone between larger political or cultural entities.
-
D.
establishesFrontier
Indicates the action or relationship by which a boundary or frontier is formally created, defined, or set between entities.
-
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_69f2247909048190ae86c2160cf8b566 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b7b03488190b1db5fde4c7dd6e5 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 7:17 p.m.