Triple
T2929761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Germania |
E78932
|
entity |
| Predicate | locatedBeyond |
P20249
|
FINISHED |
| Object | northeastern frontiers of the Roman Empire |
—
|
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: northeastern frontiers of the Roman Empire | Statement: [Germania, locatedBeyond, northeastern frontiers of the Roman Empire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedBeyond Context triple: [Germania, locatedBeyond, northeastern frontiers of the Roman Empire]
-
A.
locatedOff
Indicates that one entity is situated away from, but in the vicinity of, another entity or reference point, rather than directly on or within it.
-
B.
locatedAfter
Indicates that one entity is positioned later than another along a defined sequence, order, or spatial/temporal axis.
-
C.
locatedBetween
Indicates that one entity is positioned spatially between two other reference entities.
-
D.
laterLocation
Indicates that an entity is located at a specified place at a later time than some reference time or earlier location.
-
E.
beyond
chosen
Indicates that one entity is located or extends farther than, or outside the limits or scope of, another reference point or boundary.
- 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_69ad8b0d40b481908bc2a5fa2e73c3fb |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad98002da4819098d6448eebcafad4 |
completed | March 8, 2026, 3:38 p.m. |
| PD | Predicate disambiguation | batch_69ad9606e8348190bb19df33a2709674 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:55 p.m.