Triple
T14292071
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rajputana Rifles |
E354338
|
entity |
| Predicate | historicalRecruitmentFrom |
P113648
|
FINISHED |
| Object | Rajput communities |
—
|
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: Rajput communities | Statement: [Rajputana Rifles, historicalRecruitmentFrom, Rajput communities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalRecruitmentFrom Context triple: [Rajputana Rifles, historicalRecruitmentFrom, Rajput communities]
-
A.
historicalRecord
Indicates that there exists a documented account or record capturing information about an entity, event, or relationship from the past.
-
B.
historicallySoughtAs
Indicates that one entity has been pursued, desired, or actively sought by another entity over a historical period or in past contexts.
-
C.
staffingHistory
Indicates the record of how staffing levels or personnel assignments have changed over time for a given entity or position.
-
D.
resourceHistoricallyExtracted
Indicates that a resource was extracted from a location or entity during some period in the past, but not necessarily in the present.
-
E.
affiliationHistory
Indicates a historical record of an entity’s past and present organizational or group affiliations, including when and how those affiliations changed over time.
- F. None of above. chosen
Provenance (4 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_69d8278e17088190b328c5a9d4be74ff |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de7179368081908117a9ccfbf94fd4 |
completed | April 14, 2026, 4:55 p.m. |
| PD | Predicate disambiguation | batch_69de2a8f81f08190af737e1654847aa6 |
completed | April 14, 2026, 11:52 a.m. |
| PDg | Predicate description generation | batch_69de2e07d1f88190bdcd20967e484718 |
completed | April 14, 2026, 12:07 p.m. |
Created at: April 10, 2026, 1:11 a.m.