Triple
T38403424
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman province of Lusitania |
E900958
|
entity |
| Predicate | militaryDistrictOf |
P2804
|
FINISHED |
| Object | Hispania |
—
|
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: Hispania | Statement: [Roman province of Lusitania, militaryDistrictOf, Hispania]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: militaryDistrictOf Context triple: [Roman province of Lusitania, militaryDistrictOf, Hispania]
-
A.
militaryDistrict
chosen
Indicates that an entity functions as, or is located within, an administrative military district or region under military jurisdiction.
-
B.
parentUnitMilitaryDistrict
Indicates that one military unit is organizationally subordinate to and contained within a higher-level military district.
-
C.
regimentalDistrict
Indicates the administrative or geographic district to which a military regiment is officially assigned or associated.
-
D.
governmentalDistrictOf
Indicates that a governmental district is the administrative district to which a given entity belongs or in which it is located.
-
E.
stateMilitaryUnitOf
Indicates that a military unit is organized, controlled, or officially associated with a particular state or governmental jurisdiction.
- 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_69f76e6071a081909eea7a670d21420c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd553d7cb881908d243e7a9f30ac85 |
completed | May 8, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69fd514dcb1c81908333c70d7edd79c9 |
completed | May 8, 2026, 2:58 a.m. |
Created at: May 3, 2026, 4:31 p.m.