Triple
T11677686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nana Fadnavis |
E277533
|
entity |
| Predicate | reasonForComparison |
P94048
|
FINISHED |
| Object | use of intricate diplomacy and power politics |
—
|
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: use of intricate diplomacy and power politics | Statement: [Nana Fadnavis, reasonForComparison, use of intricate diplomacy and power politics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForComparison Context triple: [Nana Fadnavis, reasonForComparison, use of intricate diplomacy and power politics]
-
A.
similarityReason
chosen
Indicates that there is an identified basis or explanation for why two entities are considered similar.
-
B.
selectionReason
Indicates the reason or justification for choosing or selecting one entity over alternatives.
-
C.
reasonForUse
Indicates that one entity specifies the justification, purpose, or motivation for using another entity.
-
D.
reasonForChange
Indicates that one entity serves as the cause, justification, or motivation for a modification or change in another entity or state.
-
E.
comparisonType
Indicates the specific kind of comparison being made between two or more values or entities (e.g., equality, inequality, ordering, or similarity).
- F. None of above.
Provenance (3 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_69d6aafd0a448190b44da30af8c6c519 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a46000a48190888ad1a6ade052e3 |
completed | April 10, 2026, 7:18 a.m. |
| PD | Predicate disambiguation | batch_69d88a77e6e88190b7519100bde76575 |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:40 p.m.