Triple
T17996502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pole for Freedoms |
E430513
|
entity |
| Predicate | alliancesAround |
P130060
|
FINISHED |
| Object | moderate platform |
—
|
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: moderate platform | Statement: [Pole for Freedoms, alliancesAround, moderate platform]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alliancesAround Context triple: [Pole for Freedoms, alliancesAround, moderate platform]
-
A.
alliance
Indicates a formal cooperative relationship between entities who agree to support each other in shared goals or interests.
-
B.
allianceInteraction
Indicates an interaction or cooperative engagement occurring specifically between allied entities within an alliance.
-
C.
allianceScope
Indicates the extent or boundaries of cooperation and mutual obligations defined within an alliance relationship.
-
D.
allianceOrRivalry
Indicates a relationship where entities are either cooperating as allies or competing as rivals, capturing both partnership and opposition dynamics.
-
E.
allianceStructure
Indicates the organizational or relational configuration that defines how members of an alliance are structured and interconnected.
- 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_69d8b90364248190a37381adea932f42 |
completed | April 10, 2026, 8:46 a.m. |
| NER | Named-entity recognition | batch_69e4b3e4ae948190903ed255b0fe1dca |
completed | April 19, 2026, 10:52 a.m. |
| PD | Predicate disambiguation | batch_69e3f90039e4819080527f860dca042e |
completed | April 18, 2026, 9:34 p.m. |
| PDg | Predicate description generation | batch_69e42d8d68288190a05dc5d7803cf823 |
completed | April 19, 2026, 1:19 a.m. |
Created at: April 10, 2026, 10:23 a.m.