Triple
T30298112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tamil Maanila Congress |
E770574
|
entity |
| Predicate | formsAlliancesWith |
P136406
|
FINISHED |
| Object | national parties in India |
—
|
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: national parties in India | Statement: [Tamil Maanila Congress, formsAlliancesWith, national parties in India]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formsAlliancesWith Context triple: [Tamil Maanila Congress, formsAlliancesWith, national parties in India]
-
A.
soughtAllianceWith
Indicates that one entity actively attempted to form an alliance or cooperative partnership with another entity.
-
B.
formedAllianceThrough
Indicates that two or more parties established an alliance specifically by means of, or as a result of, a particular event, action, or intermediary.
-
C.
alliance
Indicates a formal cooperative relationship between entities who agree to support each other in shared goals or interests.
-
D.
alliancesAround
Indicates that alliances are formed or exist in the vicinity or context of a specified entity or focal point.
-
E.
alliesOf
chosen
Indicates that one entity is in a cooperative, supportive, or mutually beneficial alliance with another entity.
- 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_69f224881b948190b8c4921b250a44a3 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f75dc25fa08190b371faf36d9fb72c |
completed | May 3, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f758586534819083e91172f4bf5098 |
completed | May 3, 2026, 2:14 p.m. |
Created at: April 29, 2026, 7:48 p.m.