Triple
T38094382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman Empire under Trajan and Hadrian |
E951203
|
entity |
| Predicate | frontierConstruction |
P119702
|
FINISHED |
| Object | Hadrian’s Wall |
—
|
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: Hadrian’s Wall | Statement: [Roman Empire under Trajan and Hadrian, frontierConstruction, Hadrian’s Wall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: frontierConstruction Context triple: [Roman Empire under Trajan and Hadrian, frontierConstruction, Hadrian’s Wall]
-
A.
frontierSystem
Indicates a system that lies at or near the boundary or edge of a defined region, domain, or area of control.
-
B.
establishesFrontier
chosen
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.
frontierWith
Indicates that two regions or territories share a common boundary or border, especially one marking the edge of settled or controlled area.
-
E.
laterConstruction
Indicates that one construction event or structure occurred or was built after another in time.
- 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_69f76f04960c8190a83f14ae4c67f5bc |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fcc42cbac48190b8d3e4c9ce140838 |
completed | May 7, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69fcb0fc69c88190800453eb57a7e62c |
completed | May 7, 2026, 3:34 p.m. |
Created at: May 3, 2026, 4:21 p.m.