Triple
T11323210
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | States of India |
E268141
|
entity |
| Predicate | areKeyTo |
P98500
|
FINISHED |
| Object | India's federal structure |
—
|
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: India's federal structure | Statement: [States of India, areKeyTo, India's federal structure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: areKeyTo Context triple: [States of India, areKeyTo, India's federal structure]
-
A.
keyAssociation
Indicates an associative relationship where one entity serves as a key used to identify, access, or link to another entity or set of entities.
-
B.
isKeyToPlotOf
Indicates that something plays a crucial, defining role in driving or enabling the main events or structure of a plot.
-
C.
isKeyPostIn
Indicates that a post or position is a central, strategically important element within a specified organization, structure, or context.
-
D.
keyOf
Indicates that one entity functions as the key (identifier or access token) associated with another entity.
-
E.
isKeyInterchangeFor
Indicates that one location or facility serves as a primary transfer point connecting major routes, lines, or modes of transport for another.
- 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_69d6aaca5c24819083db46a30d86cb34 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9e122e48190b3f890de8d561480 |
completed | April 9, 2026, 6:03 p.m. |
| PD | Predicate disambiguation | batch_69d787ad575081908274280bf75d95fd |
completed | April 9, 2026, 11:04 a.m. |
| PDg | Predicate description generation | batch_69d796d049e88190a9fd7508f477f541 |
completed | April 9, 2026, 12:08 p.m. |
Created at: April 8, 2026, 9:32 p.m.