Triple
T2101162
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Antonine Wall |
E37094
|
entity |
| Predicate | significantFinds |
P19329
|
FINISHED |
| Object | Roman distance slabs |
—
|
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: Roman distance slabs | Statement: [Antonine Wall, significantFinds, Roman distance slabs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: significantFinds Context triple: [Antonine Wall, significantFinds, Roman distance slabs]
-
A.
finds
Indicates that one entity discovers, locates, or comes upon another entity, often as the result of a search or encounter.
-
B.
archaeologicalFindsInclude
chosen
Indicates that the set of archaeological finds at a site or context contains or encompasses the specified items or types of artifacts.
-
C.
reportsDiscoveryOf
Indicates that one entity formally announces or documents the finding or uncovering of another entity (typically a new object, fact, or phenomenon).
-
D.
significantRevisionIn
Indicates that one entity represents a substantial or important change made within another entity, such as a major update or revision occurring in a larger work or version.
-
E.
significantEvent
Indicates that an event involving the entities is of notable importance or impact within a given context.
- 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_69a8861828948190924aa30c08806b3a |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69abbabb512c819087b1d5ec8ef11e63 |
completed | March 7, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69abb7b6274081909df36cd7a7c6a675 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:43 p.m.