Triple
T19922787
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gwalior Contingent |
E478840
|
entity |
| Predicate | armedForceType |
P6154
|
FINISHED |
| Object | regular troops of a princely state |
—
|
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: regular troops of a princely state | Statement: [Gwalior Contingent, armedForceType, regular troops of a princely state]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: armedForceType Context triple: [Gwalior Contingent, armedForceType, regular troops of a princely state]
-
A.
USForceType
Indicates the type or category of U.S. military force involved in a given relationship or action.
-
B.
armedForcesBranchNumber
Indicates the specific numerical designation or identifier assigned to a branch of the armed forces within a military organization.
-
C.
militaryBranchOfGovernment
Indicates that a military organization functions as an official branch or component of a government.
-
D.
typeOfTroops
chosen
Indicates the specific category or kind of military forces involved in or associated with an entity or event.
-
E.
militaryOrganization
Indicates that an entity functions as, or is associated with, a structured armed forces or defense-related 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_69d8e521855c8190b41871700afc8d6a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e659c7be948190a65a1c78ba68dff3 |
completed | April 20, 2026, 4:52 p.m. |
| PD | Predicate disambiguation | batch_69e537f070b481908958e0e5911dcdc1 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:53 p.m.