Triple
T29502232
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Isca Augusta |
E748404
|
entity |
| Predicate | controlledRegionOf |
P82949
|
FINISHED |
| Object | territory of the Silures |
—
|
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: territory of the Silures | Statement: [Isca Augusta, controlledRegionOf, territory of the Silures]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controlledRegionOf Context triple: [Isca Augusta, controlledRegionOf, territory of the Silures]
-
A.
controlsRegion
chosen
Indicates that one entity has authoritative power or governing influence over a specified geographic or administrative region.
-
B.
occupiedRegion
Indicates that an entity has taken control of and is currently holding a specific geographic area or region.
-
C.
regulatedArea
Indicates that an area is subject to specific rules, controls, or restrictions imposed by an authority.
-
D.
guardedRegion
Indicates that a region is protected or watched over by some guarding entity or mechanism.
-
E.
coreRegionOf
Indicates that one entity constitutes the central or most essential part of another entity’s structure, area, or domain.
- 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_69f0bd455a9c8190b40a3e8ea38cf61f |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69fd02680d948190a3463fb119ba8556 |
completed | May 7, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69fcf89c69b4819082bbc564bd15137d |
completed | May 7, 2026, 8:39 p.m. |
Created at: April 28, 2026, 4:24 p.m.