Triple
T23148931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Servian reforms |
E578268
|
entity |
| Predicate | militaryRoleOfMiddleClasses |
P9463
|
FINISHED |
| Object | light infantry |
—
|
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: light infantry | Statement: [Servian reforms, militaryRoleOfMiddleClasses, light infantry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: militaryRoleOfMiddleClasses Context triple: [Servian reforms, militaryRoleOfMiddleClasses, light infantry]
-
A.
middleClass
Indicates that an entity belongs to the socioeconomic group characterized as the middle class.
-
B.
militaryRole
chosen
Indicates the specific function, position, or duty an entity holds within a military organization or context.
-
C.
traditionalSocialClass
Indicates that an entity belongs to or is associated with a particular traditional social class within a social hierarchy.
-
D.
favoredMilitaryRole
Indicates the military position, function, or specialization that an entity prefers or is most inclined to choose.
-
E.
militaryBackground
Indicates that an entity has prior or current experience, service, or training in a military organization.
- 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_69e245fb8de081908f0eba7b5fd75bc4 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18ed0b76c8190ac61b949d88e9970 |
completed | April 29, 2026, 4:53 a.m. |
| PD | Predicate disambiguation | batch_69ef89f83b108190aaaa1db6221fc163 |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 4:01 p.m.