Triple
T36821166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hispania Tarraconensis |
E909887
|
entity |
| Predicate | hadMilitaryLegions |
P86507
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Hispania Tarraconensis, hadMilitaryLegions, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadMilitaryLegions Context triple: [Hispania Tarraconensis, hadMilitaryLegions, true]
-
A.
RomanLegionsPresent
chosen
Indicates that Roman military legions are present at or within the specified location or context.
-
B.
RomanArmyType
Indicates the specific organizational or functional category to which a Roman military force belongs (e.g., legion, auxiliary, navy).
-
C.
RomanLegionsDestroyed
Indicates that one or more Roman legions were annihilated or decisively defeated, typically resulting in their destruction as effective military units.
-
D.
wasRomanMilitaryZoneSince
Indicates that a place or region has been designated and used as a Roman military zone starting from a specified point in time.
-
E.
eraOfRomanConquest
Indicates the historical period during which the Roman Empire conquered or brought the referenced entity under Roman control.
- 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_69f7ca989d50819095369c3d5af0fa2b |
completed | May 3, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69f7c89b528c8190bf80b230fc7c7108 |
completed | May 3, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:13 p.m.