Triple
T23148930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Servian reforms |
E578268
|
entity |
| Predicate | militaryRoleOfWealthy |
P9463
|
FINISHED |
| Object | heavy 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: heavy infantry | Statement: [Servian reforms, militaryRoleOfWealthy, heavy infantry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: militaryRoleOfWealthy Context triple: [Servian reforms, militaryRoleOfWealthy, heavy infantry]
-
A.
militaryRole
chosen
Indicates the specific function, position, or duty an entity holds within a military organization or context.
-
B.
wealthDescribedAs
Indicates that one entity’s wealth is characterized, portrayed, or expressed in terms of another entity or description.
-
C.
favoredMilitaryRole
Indicates the military position, function, or specialization that an entity prefers or is most inclined to choose.
-
D.
militaryImportance
Indicates the degree to which something is strategically or operationally significant to military objectives or capabilities.
-
E.
hasPrivateWealth
Indicates that an entity possesses personal financial assets or wealth that are privately owned and not part of shared or public resources.
- 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.