Triple
T8654355
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alwar State |
E205377
|
entity |
| Predicate | integratedIntoRajasthan |
P84157
|
FINISHED |
| Object | 1949 |
—
|
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: 1949 | Statement: [Alwar State, integratedIntoRajasthan, 1949]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: integratedIntoRajasthan Context triple: [Alwar State, integratedIntoRajasthan, 1949]
-
A.
namedJunagarhSince
Indicates that an entity has held the name "Junagarh" starting from a specified point in time.
-
B.
includesUnionTerritory
Indicates that an administrative or political entity contains one or more union territories within its jurisdiction or composition.
-
C.
locatedInUnionTerritory
Indicates that an entity is geographically situated within a specified union territory.
-
D.
wasMughalProvincialCapitalOf
Indicates that a place served as a provincial capital within the administrative structure of the Mughal Empire for a given province or region.
-
E.
isCouncilAreaOf
Indicates that one entity is the officially designated council (local government) area that administers or governs the other entity.
- 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_69ca8350897c819086cde7596fbe5fe7 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc48432568819093b9a867b4f62b78 |
completed | March 31, 2026, 10:18 p.m. |
| PD | Predicate disambiguation | batch_69cc45619460819091e83ffdec99c865 |
completed | March 31, 2026, 10:06 p.m. |
| PDg | Predicate description generation | batch_69cc473e44988190a3b02498e5fff668 |
completed | March 31, 2026, 10:14 p.m. |
Created at: March 30, 2026, 6:29 p.m.