Triple
T11562610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rohilla |
E274179
|
entity |
| Predicate | politicalStatus18thCentury |
P100334
|
FINISHED |
| Object | regional power in North India |
—
|
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: regional power in North India | Statement: [Rohilla, politicalStatus18thCentury, regional power in North India]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: politicalStatus18thCentury Context triple: [Rohilla, politicalStatus18thCentury, regional power in North India]
-
A.
populationStatus19thCentury
Indicates the population condition or demographic status of an entity during the 19th century.
-
B.
politicalStatusInClassicalPeriod
Indicates the political condition or standing an entity held during the classical historical period.
-
C.
statusAfter1857
Indicates the condition or state of an entity as it existed after the year 1857, typically in contrast to its prior status.
-
D.
statusAfter1815
Indicates the status or condition of an entity as it existed after the year 1815.
-
E.
gainedElectoralStatusInCentury
Indicates that an entity obtained official electoral status or recognition during a specified century.
- 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_69d6aae5ac3c81908d2b0a3a665665b2 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d88dd2016481909b33848af3d1d6c1 |
completed | April 10, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69d85dc3fc2c8190bed7e2111301a77c |
completed | April 10, 2026, 2:17 a.m. |
| PDg | Predicate description generation | batch_69d87f2e67108190ac36bf47aac12fa8 |
completed | April 10, 2026, 4:40 a.m. |
Created at: April 8, 2026, 9:37 p.m.