Triple
T466517
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ajmer-Merwara |
E8458
|
entity |
| Predicate | notAdministeredThrough |
P15019
|
FINISHED |
| Object | princely states |
—
|
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: princely states | Statement: [Ajmer-Merwara, notAdministeredThrough, princely states]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notAdministeredThrough Context triple: [Ajmer-Merwara, notAdministeredThrough, princely states]
-
A.
administeredIn
Indicates that an action, treatment, or process is carried out or applied within a specific location, context, or jurisdiction.
-
B.
administeredWithin
Indicates that one entity is given, applied, or carried out inside the spatial or temporal bounds of another entity (such as a location, container, or time period).
-
C.
typeOfAdministration
Indicates the specific form or system of administration applied to or governing an entity.
-
D.
notObservedIn
Indicates that a particular entity, event, or property has not been detected, recorded, or seen within a specified context, dataset, or environment.
-
E.
isPassedThroughBy
Indicates that something serves as a medium, route, or channel through which another thing moves, flows, or is transmitted.
- 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_69a2e7f3aeb48190a19453e3a043f486 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2efd831088190b6ac6a56b34a8816 |
completed | Feb. 28, 2026, 1:38 p.m. |
| PD | Predicate disambiguation | batch_69a2edea1acc81908a72d9f4c43438ea |
completed | Feb. 28, 2026, 1:30 p.m. |
| PDg | Predicate description generation | batch_69a2ef611b9c8190ac5e9174744d9127 |
completed | Feb. 28, 2026, 1:36 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.