Triple
T36821167
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hispania Tarraconensis |
E909887
|
entity |
| Predicate | primaryMilitaryRole |
P9463
|
FINISHED |
| Object | control of northern tribes |
—
|
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: control of northern tribes | Statement: [Hispania Tarraconensis, primaryMilitaryRole, control of northern tribes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryMilitaryRole Context triple: [Hispania Tarraconensis, primaryMilitaryRole, control of northern tribes]
-
A.
militaryRole
chosen
Indicates the specific function, position, or duty an entity holds within a military organization or context.
-
B.
favoredMilitaryRole
Indicates the military position, function, or specialization that an entity prefers or is most inclined to choose.
-
C.
formerMilitaryRole
Indicates that an entity previously held, but no longer holds, a specific military role or position.
-
D.
primaryMilitaryComponent
Indicates that one entity serves as the main or principal military element or force within the structure or composition of another entity.
-
E.
paramilitaryRole
Indicates that an entity serves in, is associated with, or performs functions for a paramilitary organization or unit.
- 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_69f76e7dd13c81908c60b05adb49eeb5 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0e039481908a4a2666f76c5363 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:13 p.m.