Triple
T8312110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Isca Silurum |
E194613
|
entity |
| Predicate | abandonedAsFortress |
P52894
|
FINISHED |
| Object | early 4th century AD |
—
|
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: early 4th century AD | Statement: [Isca Silurum, abandonedAsFortress, early 4th century AD]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: abandonedAsFortress Context triple: [Isca Silurum, abandonedAsFortress, early 4th century AD]
-
A.
abandonedAsFort
chosen
Indicates that a location or structure previously used as a fort has been given up and is no longer maintained or occupied for defensive or military purposes.
-
B.
abandonedAsPermanentSettlement
Indicates that a place or site has been given up and is no longer used as a permanent settlement.
-
C.
wasFortifiedBy
Indicates that a place or structure received defensive strengthening or fortification through the actions or resources of a specified agent or entity.
-
D.
fortifiedBuilding
Indicates that a building is strengthened or reinforced for defense against attacks or intrusions.
-
E.
usedFortificationsAt
Indicates that an entity employed or deployed specific fortifications in a particular context, such as a battle, campaign, or defensive situation.
- 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_69ca82e6e2648190a31eaf6f4f757b2a |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7f504ca8819087fb1f731f7a7cfd |
completed | March 31, 2026, 8:01 a.m. |
| PD | Predicate disambiguation | batch_69cb70bb3a708190bc705222092da614 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 5:54 p.m.