Triple
T36784649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Astures |
E908869
|
entity |
| Predicate | laterRomanProvince |
P52600
|
FINISHED |
| Object | Gallaecia |
—
|
NE NERFINISHED |
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: Gallaecia | Statement: [Astures, laterRomanProvince, Gallaecia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterRomanProvince Context triple: [Astures, laterRomanProvince, Gallaecia]
-
A.
wasRomanProvince
Indicates that one entity functioned as a province under the authority or administration of the Roman Empire.
-
B.
laterRomanAdministrativeUnit
chosen
Indicates that one entity functioned as an administrative unit within the later Roman Empire in relation to another entity.
-
C.
romanProvinceAfterConquest
Indicates that a territory became a Roman province following its military conquest by Rome.
-
D.
romanProvinceType
Indicates that an entity is classified as a specific type or category of Roman province.
-
E.
wasRomanProtectorate
Indicates that one political entity was under the protection and partial control of the Roman state as a protectorate.
- 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_69f76e7a937c81909ed7359641e670f6 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a00b7fb90f881908f73edf2be8cc3a5 |
completed | May 10, 2026, 4:53 p.m. |
| PD | Predicate disambiguation | batch_6a00b75593d08190b3e76191cd79cdec |
completed | May 10, 2026, 4:50 p.m. |
Created at: May 3, 2026, 4:12 p.m.