Triple
T25758692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arevaci |
E648673
|
entity |
| Predicate | territoryApproximateTo |
P72322
|
FINISHED |
| Object | modern provinces of Burgos |
—
|
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: modern provinces of Burgos | Statement: [Arevaci, territoryApproximateTo, modern provinces of Burgos]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: territoryApproximateTo Context triple: [Arevaci, territoryApproximateTo, modern provinces of Burgos]
-
A.
territoryCorrespondedTo
chosen
Indicates that one territory matched, aligned with, or was equivalent to another territory in scope, boundaries, or designation.
-
B.
territoryType
Indicates the specific kind or classification of a territory associated with an entity (e.g., country, region, zone, or jurisdiction type).
-
C.
refersToTerritory
Indicates that one entity designates, mentions, or is associated with a specific geographic area or territorial domain.
-
D.
territorialExtent
Indicates the geographic area or spatial range over which something extends, applies, or has jurisdiction.
-
E.
coreTerritoryAround
Indicates that one entity serves as the central or primary territory surrounding or enclosing another entity.
- 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_69e7ab314d788190b3abe19e114080e1 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f61f12b0f08190bc4a16907941864c |
completed | May 2, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69f61b37a5648190b10d33ae205ccfee |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 22, 2026, 4:43 a.m.