Triple
T27985785
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baetica |
E706739
|
entity |
| Predicate | legalDistrict |
P6190
|
FINISHED |
| Object | conventus Cordubensis |
—
|
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: conventus Cordubensis | Statement: [Baetica, legalDistrict, conventus Cordubensis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalDistrict Context triple: [Baetica, legalDistrict, conventus Cordubensis]
-
A.
hasJudicialDistrict
Indicates that an entity falls within or is associated with a specific judicial district for legal or court-related purposes.
-
B.
legalJurisdiction
chosen
Indicates the legal authority or geographic area whose laws and courts have the power to govern, regulate, or adjudicate matters involving the related entities.
-
C.
judicialDistrictBasis
Indicates the legal or administrative basis on which a particular judicial district is defined, assigned, or determined.
-
D.
countyJurisdiction
Indicates that one entity (typically a government body or authority) has legal or administrative jurisdiction over a specific county.
-
E.
districtRegion
Indicates that a district is located within or belongs administratively to a specific region.
- 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_69ef96b8b8d88190bad5e4ae966bf14e |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69fcdf2394748190b35cead3e208447d |
completed | May 7, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe344ec8190a0471911952f4b82 |
completed | May 7, 2026, 6:37 p.m. |
Created at: April 27, 2026, 7:47 p.m.