Triple
T10163782
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vallum Antonini |
E233954
|
entity |
| Predicate | usedAsBoundaryUntil |
P52351
|
FINISHED |
| Object | late 2nd century CE |
—
|
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: late 2nd century CE | Statement: [Vallum Antonini, usedAsBoundaryUntil, late 2nd century CE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsBoundaryUntil Context triple: [Vallum Antonini, usedAsBoundaryUntil, late 2nd century CE]
-
A.
isBoundaryFor
Indicates that one entity serves as the limiting edge, border, or enclosing extent that defines the spatial or conceptual bounds of another entity.
-
B.
setsBoundary
Indicates that one entity defines or forms the limiting edge or border of another entity.
-
C.
endBoundaryDefinedBy
chosen
Indicates that the endpoint or final limit of one entity is determined, marked, or delimited by another entity.
-
D.
boundaryBetween
Indicates that something serves as a dividing line or limit separating two distinct regions, areas, or entities.
-
E.
previouslyPartOfBoundaryBetween
Indicates that something once formed part of the dividing line or border between two areas or entities, but no longer does so.
- 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_69ca848e80748190b91d1e04d35512c7 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cdec6a7bb48190952f4318af9cc32b |
completed | April 2, 2026, 4:11 a.m. |
| PD | Predicate disambiguation | batch_69cd4ba795808190acc9124c98c6e40f |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:09 p.m.