Triple
T31851455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Visigothic army |
E813075
|
entity |
| Predicate | coreForces |
P18776
|
FINISHED |
| Object | noble cavalry |
—
|
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: noble cavalry | Statement: [Visigothic army, coreForces, noble cavalry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coreForces Context triple: [Visigothic army, coreForces, noble cavalry]
-
A.
componentForces
Indicates that a force is decomposed into its constituent directional components that together produce the original overall force.
-
B.
nativeForces
Indicates that certain forces or troops are indigenous to, or originate from, a particular place, group, or population.
-
C.
forces
Indicates that one entity compels or obliges another entity to perform an action or be in a certain state, typically against the latter’s will or without full freedom of choice.
-
D.
primaryForces
chosen
Indicates a relationship where one or more forces are identified as the main or dominant contributors to an effect, behavior, or outcome among all forces involved.
-
E.
governingForceOf
Indicates that one entity functions as the primary controlling or directing influence over another entity’s behavior, state, or dynamics.
- 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_69f348eb327881909b4584b925742f6e |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6b03c50ac8190a21a7721219b0167 |
completed | May 3, 2026, 2:17 a.m. |
| PD | Predicate disambiguation | batch_69f6aca59d4881908d14ed47962703bd |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 30, 2026, 11:51 p.m.