Triple
T10125631
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sandip |
E226206
|
entity |
| Predicate | politicalMethod |
P92123
|
FINISHED |
| Object | emotional agitation |
—
|
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: emotional agitation | Statement: [Sandip, politicalMethod, emotional agitation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: politicalMethod Context triple: [Sandip, politicalMethod, emotional agitation]
-
A.
politicalFunction
Indicates that an entity holds, performs, or is associated with a specific role, duty, or function within a political system or structure.
-
B.
politicalForm
Indicates the type or structure of governance or political organization that characterizes an entity.
-
C.
electionMethod
Indicates the process or system used to select a candidate or make a decision in an election.
-
D.
politicalMachine
Indicates a relationship where an organized group or network uses political influence, patronage, and coordinated actions to control or significantly sway political decisions or outcomes.
-
E.
politicalRationale
Indicates the reasoning, justification, or strategic considerations underlying a political decision, stance, or action.
- 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_69ca843057b48190a86730167f5d6b98 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cdd2ed85b4819097dfe89e044e1a90 |
completed | April 2, 2026, 2:22 a.m. |
| PD | Predicate disambiguation | batch_69cd4ba1d360819087698d04a53cc87e |
completed | April 1, 2026, 4:45 p.m. |
| PDg | Predicate description generation | batch_69cd4fed19d481909d2c7ff1114664b6 |
completed | April 1, 2026, 5:03 p.m. |
Created at: March 30, 2026, 9:05 p.m.