Triple
T8386037
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Legio XX Valeria Victrix |
E197820
|
entity |
| Predicate | roleInBritain |
P81784
|
FINISHED |
| Object | frontier defense |
—
|
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: frontier defense | Statement: [Legio XX Valeria Victrix, roleInBritain, frontier defense]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInBritain Context triple: [Legio XX Valeria Victrix, roleInBritain, frontier defense]
-
A.
regionAllocatedToBritain
Indicates that a specific geographic region has been designated or assigned to Britain’s control or authority.
-
B.
EnglishRole
Indicates that one entity serves a particular role or function within the context of the English language for another entity.
-
C.
roleInMonarchyPeriod
Indicates that an entity held a specific role or position during a defined period of a monarchy.
-
D.
locatedInBritishCountry
Indicates that one entity is geographically or administratively situated within a country that is part of the United Kingdom.
-
E.
roleInEurope
Indicates that an entity holds a specific function, position, or responsibility within a European context, such as within Europe as a region or its institutions.
- F. None of above. chosen
Provenance (4 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_69ca82f749388190bffbea6dfb509016 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb80e1bcdc81909111aa33ee996e0a |
completed | March 31, 2026, 8:08 a.m. |
| PD | Predicate disambiguation | batch_69cb70cfe82881909fe374ba52649e84 |
completed | March 31, 2026, 6:59 a.m. |
| PDg | Predicate description generation | batch_69cb76da264881909483b835e1db06da |
completed | March 31, 2026, 7:25 a.m. |
Created at: March 30, 2026, 6:02 p.m.