Triple
T28219462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mogontiacum |
E711411
|
entity |
| Predicate | onFrontier |
P128408
|
FINISHED |
| Object | Rhine 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: Rhine frontier | Statement: [Mogontiacum, onFrontier, Rhine frontier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: onFrontier Context triple: [Mogontiacum, onFrontier, Rhine frontier]
-
A.
frontierSystem
chosen
Indicates a system that lies at or near the boundary or edge of a defined region, domain, or area of control.
-
B.
establishesFrontier
Indicates the action or relationship by which a boundary or frontier is formally created, defined, or set between entities.
-
C.
northernFrontier
Indicates that one entity serves as the northern boundary, edge, or frontier region relative to another entity.
-
D.
wasFrontierRegion
Indicates that a region historically functioned as a frontier area, marking a boundary or border zone between larger political or cultural entities.
-
E.
frontsOn
Indicates that one entity directly faces, borders, or has its primary side along the edge of another entity, such as a building fronting on a street or a property fronting on a body of water.
- 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_69efb51dfb048190ada79b745c33b363 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f6434f9f888190bd43fde92cd729fe |
completed | May 2, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69f63c6c1a948190b68c0f92c264cc0c |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 10:45 p.m.